[Github-comments] [geany/geany] Unexpected behavior from UNDO when using seach-replace -> in session (#1631)

elextr notifications at xxxxx
Sat Oct 7 23:03:45 UTC 2017


There is no global undo stack.  Each file has its own undo stack since most editing makes changes to one file and not any of the others.  When you do a session change each file has the change made independently and the undo is saved to its stack.  Of course files where nothing was changed have no undo, so globally undoing the last undo entry is a "bad thing".

In general changing files other than the current one is a "bad thing" except when explicitly instructed by the user (eg replace in session).  

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1631#issuecomment-334971493
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20171007/c3405d13/attachment.html>


More information about the Github-comments mailing list