From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: %f of gnus-summary-line-format
Date: 16 Jan 1999 00:11:49 +0100 [thread overview]
Message-ID: <m390f4dtca.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Michael Cook's message of "15 Jan 1999 16:42:30 -0500"
Michael Cook <cook@sightpath.com> writes:
> I'll submit a patch that removes all the help strings.
For this particular variable, listing all things that influence all
the format specs is beyond what one can comfortably put in a doc
string. Doc strings are for easy reference when tinkering -- after
you've read the manual.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-01-15 23:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-15 16:13 Michael Cook
1999-01-15 16:21 ` Lee Willis
1999-01-15 16:58 ` Michael Cook
1999-01-15 21:24 ` Lars Magne Ingebrigtsen
1999-01-15 21:42 ` Michael Cook
1999-01-15 23:11 ` Lars Magne Ingebrigtsen [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=m390f4dtca.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).