From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: summary buffer keys: don't do different things behind my back
Date: Sun, 05 Jan 2003 05:08:08 +0100 [thread overview]
Message-ID: <m3n0mgxmqf.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m2it92qgbi.fsf@dan.jacobson.tw>
Dan Jacobson <jidanni@deadspam.com> writes:
> Idea: in some types of Summaries, the E command won't really ever
> actually delete a message, and some other keys also might not really
> do what they might do in other Summary buffers.
The `E' command doesn't delete anything in any buffers, as far as I
know.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
parent reply other threads:[~2003-01-05 4:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <m2it92qgbi.fsf@dan.jacobson.tw>]
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=m3n0mgxmqf.fsf@quimbies.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).