From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@jurta.org>, 16651@debbugs.gnu.org
Subject: bug#16651: 24.3.50; desktop saves temporary buffers
Date: Wed, 5 Feb 2014 09:05:21 -0800 (PST) [thread overview]
Message-ID: <693f56c8-302d-4459-82bc-460fe65295c6@default> (raw)
In-Reply-To: <87eh3ing77.fsf@mail.jurta.org>
> With the desktop mode enabled and `C-h S info-lookup-symbol RET'
> info-look.el creates a temporary buffer with the name " temp-info-
> look"
> that is saved to the desktop because this buffer is in Info mode
> saved by `Info-desktop-buffer-misc-data'.
>
> I see two possible solutions: skip saving all buffers with the
> leading space in the buffer name, or if this problem is Info
> specific
> then fix it in `Info-desktop-buffer-misc-data' to return nil for
> Info buffers with the leading space in the buffer name.
I'm not following this thread - please excuse any ignorance
wrt this topic.
If the question of whether to save buffers whose name begins
with a space is being posed then why not leave that up to the
user, by providing an option to decide it?
Or if you think that users might want even more control, saving
some but not all such buffers, maybe:
* By default, exclude such buffers (and perhaps other kinds of
"insignificant" buffers or buffers that are difficult to
re-create or whatever).
* Provide an option that users can use to specify particular
buffers or a regexp matching buffers that should not be
excluded.
I'm guessing that it can be hard for Emacs to guess just what
users will need/want in this regard, and so it is better to
define a reasonable default behavior but also give users a
way to override that.
next prev parent reply other threads:[~2014-02-05 17:05 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 [this message]
2014-02-05 21:42 ` Glenn Morris
2014-02-05 22:07 ` Drew Adams
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=693f56c8-302d-4459-82bc-460fe65295c6@default \
--to=drew.adams@oracle.com \
--cc=16651@debbugs.gnu.org \
--cc=juri@jurta.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).