From: jidanni@jidanni.org
To: ding@gnus.org
Subject: mention antidotes in docstrings
Date: Sat, 08 May 2010 08:47:35 +0800 [thread overview]
Message-ID: <87y6fvnrrs.fsf@jidanni.org> (raw)
gnus-summary-hide-all-threads's docstring should mention its antidote (T
S), in case one can't figure out how to rid the effects of what one has
just typed.
T S's docstring should also mention T H.
Same with other such pairs.
You might argue that if one is smart enough to do C-h l to view what one
has just typed, one should be able to hunt down the antidote. But that
is not always the case.
reply other threads:[~2010-05-08 0:47 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=87y6fvnrrs.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--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).