You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This option would allow the plugin to automatically create an edit after a chosen time.
So, in case I set this to 60 minutes: if I write for 30 minutes and then pause for 60 minutes, the edit created in dropdown would be lateron created with the timestamp of the last writing action.
In some way, it is quite the opposite of the "Minimum second between edits" function. But my suggestion focuses on creating edits along the lines of actual editing actions and does not postpone them to another future edit, merging two actions that might be far apart in time.
The text was updated successfully, but these errors were encountered:
I think what you suggest would be better implemented as "only create a new edit after X seconds of inactivity" (using a fixed interval like you suggest would still split edits that were done close in time). The benefit being, as you mention, that edits that were done close in time will be saved together, since the current scheme can merge edits that were done far apart in time.
One problem is that Obsidian only calls the change event once the text has been changed, which means that the "far apart edit" has already been done and the previous diff cannot be calculated. This means the implementation would actually be something like "merge the current edit with the previous one if done in less than X seconds apart, otherwise create a new entry".
That's something I also wanted to do and I think it could work.
This option would allow the plugin to automatically create an edit after a chosen time.
So, in case I set this to 60 minutes: if I write for 30 minutes and then pause for 60 minutes, the edit created in dropdown would be lateron created with the timestamp of the last writing action.
In some way, it is quite the opposite of the "Minimum second between edits" function. But my suggestion focuses on creating edits along the lines of actual editing actions and does not postpone them to another future edit, merging two actions that might be far apart in time.
The text was updated successfully, but these errors were encountered: