Ihor Radchenko <[email protected]> writes:
I've pushed another set of `org-inside' updates to try:
1. Switched to a general `org-hidden-text-functions' hook, which can
be expanded in the future for other hidden types.
2. Anticipate v31 buffer-local `window-buffer-change' capabilities.
3. Attempt to handle property setting correctly for <v31 and v31+
(untested).
4. Implement a custom-set function for live appearance updates.
5. Use `org-element' instead of property scanning to identify bounds
of entities.
and a few other cleanups. Please test. In particular, I am not yet
setup on v31, so if you could test and compare behavior on v30 vs. v31
(Jens?), I'd appreciate. Testing should including entry/exit and adding
text before/after the markers. Also ensure changing to another buffer
clears the overlay correctly.
One difference that should be expected between v30 and v31: when the
markers are unhidden (auto or via `org-inside-toggle-hidden'), you can
place point before the first marker while markers remain unhidden, but
moving after the last visible marker re-hides them.
This is because I use the same overlay to bring in appearance changes
and a wider `cursor-sensor-functions' range for exiting. The updated
firing behavior of v31 (respecting default rear-stickiness of the
`cursor-sensor-functions' and presumably the equivalent "rear-advance"
overlay property) /should/ result in a slight behavior difference when
moving point to the end with visible markers. Not easy to workaround,
and the v31 behavior (I expect) is better, so thinking of leaving as is.
