From: Lennart Borgman <lennart.borgman.073@student.lu.se>
Cc: "Richard M. Stallman" <rms@gnu.org>, emacs-devel@gnu.org
Subject: Re: Faces customization group linked from mode groups
Date: Sat, 05 Nov 2005 20:59:16 +0100 [thread overview]
Message-ID: <436D0F14.7000908@student.lu.se> (raw)
In-Reply-To: <87hdarodih.fsf@jurta.org>
Juri Linkov wrote:
>>There was recently a question on the gnu-emacs-help list from someone
>>trying to customize the faces used in syntax highlighting C mode. He
>>looked in C mode customization group but could not find it.
>>
>>Maybe it would be a good idea to have a link to the faces customization
>>from each mode customization group? (If that is possible in a simple way?)
>>
>>
>
>One solution is to add the parent group `font-lock-highlighting-faces'
>to all groups of modes that support font-lock. But this has one negative
>effect: the `group' link is two-directional, so the customization group
>`font-lock-highlighting-faces' will display too many children links
>to all such groups.
>
>
Is not this the opposite way of the way Richard suggested? But the
problem you mention should essentially be the same, or?
>A better solution is to implement a new one-directional link to another
>customization group. Currently `:link' supports four link types, and a
>new link type could have the name `custom-group'. It could create a
>one-directional link in the customization buffer leading to the specified
>group, e.g.:
>
>(defgroup c nil
> "Support for the C language and related languages."
> :link '(custom-manual "(ccmode)") ;; this is already existing link
> :link '(custom-group font-lock-highlighting-faces) ;; a new link type
> :group 'languages)
>
>
To me this seems like the way to go.
When it comes to updating these defgroup:s, is there an easy way to find
all these modes?
next prev parent reply other threads:[~2005-11-05 19:59 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 [this message]
2005-11-06 17:35 ` Richard M. Stallman
2005-11-07 14:27 ` Juri Linkov
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=436D0F14.7000908@student.lu.se \
--to=lennart.borgman.073@student.lu.se \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.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.
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).