From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Adding :link '(custom-manual ...) in defcustom (was: CVS update of gnus/lisp (ChangeLog message.el))
Date: Fri, 28 Nov 2003 23:58:50 +0100 [thread overview]
Message-ID: <v91xrs85hx.fsf_-_@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m365h4yvry.fsf@defun.localdomain>
On Fri, Nov 28 2003, Jesper Harder wrote:
> "Reiner Steib" <reiner.steib@gmx.de> writes:
>
>> Modified: ChangeLog message.el
>>
>> Added custom-manual links to all variables that have
>> an index entry in the message manual.
>
> I'm not sure that this is really a good idea.
>
> It's probably nice when you use `customize-option', but it makes
> `customize-group' awfully cluttered with a lot of identical and
> redundant links.
`M-x customize-group RET gnus-article-treat RET' ;-)
I'm now aware of a policy when to add them and when not. Any
pointers? [1] And I couldn't see any usage pattern. I thought that
they were just missing, because the programmer forgot to add them in
the first place.
I don't have any problem with reverting my patch. But I don't
understand the purpose of the ":link" entry then.
Bye, Reiner.
[1] (info "(elisp)Variable Definitions") doesn't mention :link at all.
`C-h f defcustom RET' neither.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2003-11-28 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1APqoO-0003Ah-00@quimby.gnus.org>
2003-11-28 22:26 ` CVS update of gnus/lisp (ChangeLog message.el) Jesper Harder
2003-11-28 22:58 ` Reiner Steib [this message]
2003-11-28 23:52 ` Adding :link '(custom-manual ...) in defcustom Reiner Steib
2003-11-29 9:01 ` Jesper Harder
2003-11-30 14:07 ` Per Abrahamsen
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=v91xrs85hx.fsf_-_@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.de \
/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).