From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: 'e' in the summary buffer leads to lost work
Date: 27 Feb 1998 12:57:26 +0100 [thread overview]
Message-ID: <m3iuq1l0pl.fsf@sparky.gnus.org> (raw)
In-Reply-To: "Edward J. Sabol"'s message of "Mon, 23 Feb 1998 16:40:34 -0500"
"Edward J. Sabol" <sabol@alderaan.gsfc.nasa.gov> writes:
> I like this solution the best. The buffer name should be based on various
> header fields in the e-mail.
Ok; I've put this on the todo list.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-02-27 11:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-23 21:30 Matt Armstrong
1998-02-23 21:40 ` Edward J. Sabol
1998-02-23 23:20 ` Paul Franklin
1998-02-24 15:48 ` jari.aalto
1998-02-27 11:57 ` Lars Magne Ingebrigtsen [this message]
1998-02-27 9:24 ` Harry Putnam
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=m3iuq1l0pl.fsf@sparky.gnus.org \
--to=larsi@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).