From: Drew Adams <drew.adams@oracle.com>
To: Glenn Morris <rgm@gnu.org>, Juri Linkov <juri@jurta.org>
Cc: 16651@debbugs.gnu.org
Subject: bug#16651: 24.3.50; desktop saves temporary buffers
Date: Wed, 5 Feb 2014 14:07:27 -0800 (PST) [thread overview]
Message-ID: <99777fab-ca72-4035-b77b-6b799fc44357@default> (raw)
In-Reply-To: <vg61otnsnf.fsf@fencepost.gnu.org>
> > I see two possible solutions: skip saving all buffers with the
> > leading space in the buffer name,
>
> I cannot imagine any reason why such buffers should ever be
> saved in a desktop.
Many, perhaps most, things a user might want (or might do)
cannot be imagined, by even the most imaginative of designers.
"Should" in such a context, can be applied reasonably only
to the _default_ behavior.
A user doing something that involves _display_ of temporary
buffers (which include buffers such as `*Pp Eval Output*',
`*Messages* and `*scratch*', as well as _internal_ buffers,
which are buffers whose names start with a space) might well
want to save the current Emacs state, including the display of
such a buffer.
There is no sense in deciding the behavior in a black-and-white,
one-size-fits-all way. One reasonable default behavior would
be to exclude such buffers from saving, but users should be
able to easily customize this.
Another reasonable default behavior would be to exclude all
such buffers that are not displayed. It is rare that such a
buffer is displayed, and if that happens it is the user who
has forced it. Emacs should not assume that a displayed
buffer should not be saved (except by default).
In most cases the state (e.g. contents) of a temporary buffer
cannot be restored, in any case. But the display of such
a buffer can be recorded and restored. A user might well
position `*Messages*' or `*Buffer List*' specially and want
that display to be restored, regardless of the current
buffer contents.
An internal buffer that is displayed is no different in this
respect.
But again, whatever the default behavior, let users override
it easily.
next prev parent reply other threads:[~2014-02-05 22:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 7:58 bug#16651: 24.3.50; desktop saves temporary buffers Juri Linkov
2014-02-05 17:05 ` Drew Adams
2014-02-05 21:42 ` Glenn Morris
2014-02-05 22:07 ` Drew Adams [this message]
2014-02-06 8:45 ` Juri Linkov
2014-02-06 8:44 ` Juri Linkov
2014-02-06 9:06 ` Andreas Schwab
2014-02-07 7:53 ` Juri Linkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=99777fab-ca72-4035-b77b-6b799fc44357@default \
--to=drew.adams@oracle.com \
--cc=16651@debbugs.gnu.org \
--cc=juri@jurta.org \
--cc=rgm@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).