On 08/11/2009 12:00 PM, Pavel Sanda wrote:
Richard Heck wrote:
I propose something along the following lines, but I am not at all sure
about this. I'm trying to do two things here. (i) Check whether a Buffer is
dirty whenever it is destroyed. I see this as a last ditch effort to avoid
dataloss, and one that should rarely if ever be triggered. Indeed, in some
ways I'm inclined to assert here...after saving!
I realized that doesn't work right. If you've already said you don't
want to save it, you get asked again. I guess we could have some flag to
indicate you've already been asked.
(ii) Do the same check
whenever a tab is hidden. I don't think dirty tabs should be allowed to be
hidden. It will lead to surprises later.
doesnt it break multiple windows view? ie the buffer might be dirty, but i want
to have different set of visible buffers in each window, so in the second
window the dirty one could be unvisible and thats fine imho.
I don't think it breaks it, no. The point here is just to make you save
it before you hide it. It can be dirty and hidden in one view, but not
in all views. I think. If you like, I suppose we could check if it's
open in some other view.
Richard
