From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: VMized message buffer generation
Date: 02 Jun 1996 17:25:13 +0200 [thread overview]
Message-ID: <x6rary8bza.fsf@eyesore.no> (raw)
The message buffers will now be called things like "*reply to Some
Person*" while you're composing them, and after you've sent them they
are renamed to "*sent reply to Some Person*". A variable
(`message-max-buffers', default 10) says how many of these "sent"
headers to keep hanging around before killing them.
I think this'll probably be more convenient for most people. You can
get the old behavior back by setting `message-generate-new-buffers' to
nil.
--
"Yes. The journey through the human heart
would have to wait until some other time."
reply other threads:[~1996-06-02 15:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=x6rary8bza.fsf@eyesore.no \
--to=larsi@ifi.uio.no \
/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).