From: Emerick Rogul <emerick@csa.bu.edu>
Subject: Re: Getting rid of *sent ... buffers
Date: Thu, 06 Feb 2003 14:16:45 -0500 [thread overview]
Message-ID: <vuo1y2l5iea.fsf@csa.bu.edu> (raw)
In-Reply-To: <87znp9tsp4.fsf@china.shootybangbang.com>
John Paul Wallington writes:
> Peter Davis wrote:
>> Is there a way to tell gnus/message-mode to
>> automatically close the buffer once the message is sent?
> Yup. See variable `message-kill-buffer-on-exit'.
Just out of curiosity, is there a reason that
message-kill-buffer-on-exit defaults to nil rather than t? I can't
understand why you would want to keep a reply buffer around after the
message has been sent, although I'm sure there must be some reason.
-Emerick
--
-------------------------------------------------------------------------
Emerick Rogul /\/ "how young are you, how old am i?
emerick@cs.bu.edu /\/ let's count the rings around my eyes."
------------------------------------------------- 'i will dare', the mats
next prev parent reply other threads:[~2003-02-06 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <adh98rlj.fsf@bitstream.com>
2003-02-06 14:00 ` John Paul Wallington
2003-02-06 19:16 ` Emerick Rogul [this message]
[not found] ` <84r8alv4dg.fsf@lucy.is.informatik.uni-duisburg.de>
2003-02-06 16:41 ` Peter Davis
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=vuo1y2l5iea.fsf@csa.bu.edu \
--to=emerick@csa.bu.edu \
/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).