From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: custom v. *
Date: 15 Feb 1998 15:43:14 +0100 [thread overview]
Message-ID: <rjiuqhylml.fsf@zuse.+dina.kvl.dk> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "13 Feb 1998 21:21:06 +0100"
Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
> There are apparently lots of Gnus variables that have doc strings that
> do not start with "*" that are customizable. Is that inconsistent
> with how things are supposed to be?
No, it is quite right.
>From the emacs lisp manual:
A variable's documentation string should start with `*' if the
variable is one that users would often want to set
interactively. If the value is a long list, or a function, or
if the variable would only be set in init files, then don't
start the documentation string with `*'.
The quick test is:
Would the user ever set this with `M-x set-variable RET'?
next prev parent reply other threads:[~1998-02-15 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-13 20:21 Lars Magne Ingebrigtsen
1998-02-13 22:53 ` Felix Lee
1998-02-14 14:17 ` Lars Magne Ingebrigtsen
1998-02-15 14:43 ` Per Abrahamsen [this message]
1998-02-15 14:48 ` Per Abrahamsen
1998-02-15 15:14 ` Lars Magne Ingebrigtsen
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=rjiuqhylml.fsf@zuse.+dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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).