emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: address@hidden: modeline doesn't divulge buffer will go bye bye]


From: Richard Stallman
Subject: Re: address@hidden: modeline doesn't divulge buffer will go bye bye]
Date: Fri, 28 Jun 2002 11:41:12 -0600 (MDT)

    So how about a variable like `ask-about-saving-user-scratch-buffers',
    with `nil' meaning `never' (the current behavior), `ask' meaning ask the
    above question and if so treat them like unsaved file-buffers, and any
    other non-nil value meaning always treat them like unsaved file-buffers.

That sounds good.

    That's similar to setting `buffer-offer-save' to t by default and
    forcing modes that create temporary, discardable buffers to explicitly
    set it to nil, isn't it?

It is similar, but I think it is good to have a separate option
to control this, and it is better for that option to take effect
when you exit rather than when you create the buffer.  So there needs
to be a way to distinguish these buffers from other buffers.

Perhaps a value `maybe' for `buffer-offer-save' would be the way to do
it.  When `buffer-offer-save' has that value, during saving before
exit, `offer-saving-scratch-buffers' would be obeyed.

As for the easy way to set up that value for `buffer-offer-save',
perhaps `switch-to-buffer' could do this whenever it creates a buffer.
That way, all the Lisp programs that create buffers would not be
affected.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]