Le 13/07/2012 00:24, Pavel Sanda a écrit :
Richard Heck wrote:
This leads to the harmless message above, but more importantly, it means
that the undo stack is lost every time a file is saved-as. This looks like
a regression to me.
Richard, would it seem right to add a parameter to Buffer::reload asking
to preserve the undo stack in this case?
You mean to preserve undo stack for each reload of file or just for save-as
scenario? We also reload automatically after commit/checkout VCS operation which
can change read-only status.
This is why I propose to add a parameter to reload telling whether undo
should be discarded.
OTOH, it looks like doing a reload in after save-as is a bit harsh. Is
the goal only to sanitize IncludeInset?
I have been pondering for some time whether the updateBuffer mechanism
could be extended with an enum telling what to update, in order to be
able to run it for specific tasks. For example
updateBuffer(EXTERNAL_FILES) could check the validity of all external
files we hold. I had other applications in mind, but I can't remember
them ATM.
JMarc
