From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Adding :link '(custom-manual ...) in defcustom
Date: Sat, 29 Nov 2003 10:01:51 +0100 [thread overview]
Message-ID: <m3r7zry2dc.fsf@defun.localdomain> (raw)
In-Reply-To: <v91xrs85hx.fsf_-_@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Fri, 28 Nov 2003 23:58:50 +0100")
Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
> On Fri, Nov 28 2003, Jesper Harder wrote:
>
>> 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' ;-)
Exactly!
> 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.
The following isn't quite how Custom currently works, but it might be
a solution:
You can currently add a link in `defgroup'. If the link in
`defcustom' would be same as in the group it can be omitted -- it
ought to be enough to list the same link just once per group.
If `customize-option' was changed to grab links from the parent
group of the option, then we wouldn't need to add links to
individual options (unless the link is different from the group's).
next prev parent reply other threads:[~2003-11-29 9:01 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 ` Adding :link '(custom-manual ...) in defcustom (was: CVS update of gnus/lisp (ChangeLog message.el)) Reiner Steib
2003-11-28 23:52 ` Adding :link '(custom-manual ...) in defcustom Reiner Steib
2003-11-29 9:01 ` Jesper Harder [this message]
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=m3r7zry2dc.fsf@defun.localdomain \
--to=harder@ifa.au.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).