From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Default custom group
Date: Wed, 18 May 2005 18:44:39 -0400 [thread overview]
Message-ID: <E1DYXHL-00062d-CL@fencepost.gnu.org> (raw)
In-Reply-To: <b9yvf5hxdit.fsf@jpl.org> (message from Katsumi Yamaoka on Wed, 18 May 2005 15:18:50 +0900)
I'm sorry for insufficient information. It was caused by the
following form which didn't specify the parent group.
(defgroup smime nil
"S/MIME configuration.")
That ought to be fixed, and likewise any other defgroups that fail
to specify a parent.
Yesterday, I changed my mind and added the ``:group 'something''
argument to every defgroup, defface and defcustom forms in which
it hasn't been specified in Gnus (the changes will be propagated
into the Emacs trunk after a while).
Thank you. (What is the upper bound on "a while"?)
At that time, I felt like
to add some first-level groups (e.g., cryptograph, security, etc.)
is necessary.
Maybe you are right. It would not be hard to add first-level groups
now; it won't break anything. However, I want to consider the question
carefully. For instance, it doesn't make sense to add both cryptography
and security as first-level groups; the latter includes the former.
next prev parent reply other threads:[~2005-05-18 22:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 15:12 Default custom group Richard Stallman
2005-05-16 5:56 ` Katsumi Yamaoka
2005-05-17 21:23 ` Daniel Brockman
2005-05-18 22:45 ` Richard Stallman
2005-05-18 5:20 ` Richard Stallman
2005-05-18 6:18 ` Katsumi Yamaoka
2005-05-18 22:44 ` Richard Stallman [this message]
2005-05-18 23:00 ` Katsumi Yamaoka
2005-05-18 22:44 ` Richard 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=E1DYXHL-00062d-CL@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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).