From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Patch to message.el to allow saving multiple message buffers when Gnus not running
Date: Thu, 25 Sep 2008 08:04:47 -0500 [thread overview]
Message-ID: <86iqsk9y1c.fsf@lifelogs.com> (raw)
In-Reply-To: <871vzavita.fsf@marauder.physik.uni-ulm.de>
On Tue, 23 Sep 2008 20:05:53 +0200 Reiner Steib <reinersteib+gmane@imap.cc> wrote:
RS> On Mon, Sep 15 2008, Ted Zlatanov wrote:
>> On Fri, 12 Sep 2008 12:26:37 -0400 Francis Litterio <flitterio@gmail.com> wrote:
>>
FL> In Gnus in CVS Emacs, function message-set-auto-save-file-name (in
FL> message.el) arranges for all message composition buffers to be saved to
FL> the same disk file when Gnus has not been started. If two messages are
FL> being composed at the same time, both will be saved to the same file.
>>
FL> This is at odds with how the same function saves multiple drafts of
FL> outgoing messages in the drafts folder when Gnus has been started. The
FL> below patch fixes this by changing message-set-auto-save-file to append
FL> a unique timestamp to the name of the disk file for the message
FL> composition buffer.
RS> I'm not sure about the purpose of the current implementation. How is
RS> the user supposed to recover the file(s) (without and with your
RS> patch)?
I think it simply provides a fallback in case of an emergency. I don't
really know what a user-side function to recover from those files would
do. Open the files in message-mode? All of them? Then what?
Ted
next prev parent reply other threads:[~2008-09-25 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 16:26 Francis Litterio
2008-09-15 17:41 ` Ted Zlatanov
2008-09-23 18:05 ` Reiner Steib
2008-09-25 13:04 ` Ted Zlatanov [this message]
2008-09-25 16:58 ` Reiner Steib
2008-09-25 19:08 ` Francis Litterio
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86iqsk9y1c.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).