Very often, I will hit undo, only to find that all of the changes it
makes are hidden in a folded subtree. Combined with the lack of a
non-buggy true redo, this makes things very confusing.
Is there a way to fix this?
--
Myalgic encephalomyelitis denialists are knowingly causing further
Not that I know. Maybe some advice around the undo function,
to make at least point visible after an undo command? This is
untested, and may be incomplete since it does not take into
account the range in the buffer that was really affected by the undo.
But it may already help:
(defadvice undo
