-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle markers properly #22
Comments
It looks like grabbing and copying all the markers is not possible: |
As a workaround until we've found a permanent solution, we could create a list |
Yes. The important thing is that we actually don't need to handle all markers in a buffer. It is also hard to identify which markers should be checked by us for all existing packages. I think it is a good choice that only registered markers will be handled properly. In the case of In my understanding, the markers will not be actually copied but forked from the original marker for editing works in |
PR #21 by @takaxp fixes a problem with
org-clock-marker
, but this problem is a symptom of a deeper problem, that we don't currently handle markers in the undo-propose buffers.References
primitive-undo
in simple.el, in particular these lines which handle marker adjustments.Additional Notes
There are entries in the undo-list which adjust marker positions. When in the undo-propose buffer,
(eq (marker-buffer m) (current-buffer))
is false so these entries are skipped.One possible way to handle markers would be to copy the markers over to the undo-propose buffer, and edit entries in the undo-list to use the new markers.
The text was updated successfully, but these errors were encountered: