From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: why are sent buffers not burried.
Date: Sat, 24 Sep 2022 08:32:56 +0200 [thread overview]
Message-ID: <87pmflb7tz.fsf@mat.ucm.es> (raw)
In-Reply-To: <87zgeq9idg.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 575 bytes --]
Uwe> Hi
Uwe> When I run ibuffer (or buffer list), I see
Uwe> *sent wide repl... 1125 Message ~/News/drafts/drafts/55
Uwe> Why aren't these buffers burried after sending. I mean keeping them
Uwe> might be useful in some scenarios but in general it might be
annoying.
Uwe> Is there any variable that controls that?
> message-kill-buffer-on-exit is a variable defined in `message.el'.
> Its value is t
> Original value was nil
> Non-nil means that the message buffer will be killed after sending a message.
Thanks!
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
prev parent reply other threads:[~2022-09-24 6:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 16:07 Uwe Brauer
2022-09-23 16:15 ` Robert Pluim
2022-09-24 6:32 ` Uwe Brauer [this message]
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=87pmflb7tz.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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).