From: Glenn Morris <rgm@gnu.org>
To: Juri Linkov <juri@jurta.org>
Cc: 16651@debbugs.gnu.org
Subject: bug#16651: 24.3.50; desktop saves temporary buffers
Date: Wed, 05 Feb 2014 16:42:12 -0500 [thread overview]
Message-ID: <vg61otnsnf.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87eh3ing77.fsf@mail.jurta.org> (Juri Linkov's message of "Wed, 05 Feb 2014 09:58:52 +0200")
Juri Linkov wrote:
> 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.
next prev parent reply other threads:[~2014-02-05 21:42 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 [this message]
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=vg61otnsnf.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--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).