From: Juri Linkov <juri@jurta.org>
Cc: lennart.borgman.073@student.lu.se, emacs-devel@gnu.org
Subject: Re: Faces customization group linked from mode groups
Date: Mon, 07 Nov 2005 16:27:42 +0200 [thread overview]
Message-ID: <87irv4d00h.fsf@jurta.org> (raw)
In-Reply-To: <E1EYoQe-0001kP-W3@fencepost.gnu.org> (Richard M. Stallman's message of "Sun, 06 Nov 2005 12:35:40 -0500")
> Is not this the opposite way of the way Richard suggested? But the
> problem you mention should essentially be the same, or?
>
> The possible problem is that a custom buffer for
> font-lock-highlighting-faces would include lots of parent groups.
> I agree it would be nicer to add a one-way link.
To my surprise the suitable link type is already implemented but not
documented. The name of such one-way link type is `custom-group-link'.
After adding it for example to the `cpp' group like:
(defgroup cpp nil
"Highlight or hide text according to cpp conditionals."
:group 'c
:link '(custom-group-link :tag "Font Lock Highlighting Faces group"
font-lock-highlighting-faces)
:prefix "cpp-")
it displays in the customization buffer an additional line:
See also [Font Lock Highlighting Faces group].
with the button that creates a new customization buffer with the
`font-lock-highlighting-faces' group.
The cost is adding this link is losing another link in the same buffer
which looks like:
Parent documentation: [Manual].
It seems the logic of Customize assumes that if the group has a link
explicitly specified in `defgroup', then adding another default link
to the parent manual is not necessary. I don't think this logic is valid
for `custom-group-link' link type.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2005-11-07 14:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 22:03 Faces customization group linked from mode groups Lennart Borgman
2005-11-05 7:43 ` Juri Linkov
2005-11-05 19:59 ` Lennart Borgman
2005-11-06 17:35 ` Richard M. Stallman
2005-11-07 14:27 ` Juri Linkov [this message]
2005-11-07 21:56 ` Richard M. Stallman
2005-11-08 12:45 ` Juri Linkov
2005-11-11 7:42 ` Richard M. Stallman
2005-11-11 19:34 ` Juri Linkov
2005-11-12 17:50 ` Richard M. Stallman
2005-11-15 0:48 ` Juri Linkov
2005-11-15 23:21 ` Richard M. Stallman
2005-11-15 0:42 ` Juri Linkov
2005-11-15 23:21 ` Richard M. Stallman
2005-11-17 7:46 ` Juri Linkov
2005-11-18 16:57 ` Richard M. Stallman
2005-11-07 14:28 ` Juri Linkov
2005-11-05 14:35 ` Richard M. Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87irv4d00h.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman.073@student.lu.se \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).