> Maybe Scintilla needs to export some controls, such as resetting when the
> user does reload, although of course that can be undone, so maybe not.
Some downstream projects have actually resorted to emptying the undo buffer on
file reload, then toggling Scintilla's edit tracker off and on, to
Merged #3591 into master.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3591#event-10636308048
You are receiving this because you are subscribed to this thread.
Message ID:
Fine with me
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3591#issuecomment-1757418527
You are receiving this because you are subscribed to this thread.
Message ID:
As said earlier, I also vote for disabling the feature by default.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3591#issuecomment-1757381211
You are receiving this because you are subscribed to this thread.
Message ID:
BTW looking at https://scintilla.org/ScintillaDoc.html#ChangeHistory, if we
only showed `!SC_MARKNUM_HISTORY_SAVED` (e.g. display what's *not* saved to
disk) it could be a lot easier to grasp, and probably more useful as well. But
that's for later I think :)
--
Reply to this email directly
Maybe Scintilla needs to export some controls, such as resetting when the user
does reload, although of course that can be undone, so maybe not. Agree off by
default until we get more experience with it.
--
Reply to this email directly or view it on GitHub:
Agree. I was very surprised when I first saw it and thought "what went wrong
with git-changebar?" and it definitely lead to some confusion for me.
Also a suggestion of some possible improvements that could be done in the
future:
* make the colors configurable, possibly in `filetypes.common`
*
