> In <[EMAIL PROTECTED]> Richard Stallman wrote:
> 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
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 m
By the way, I noticed the new bytecomp doesn't warn to the
defcustom form in which the parent group is not specified.
Strange, I thought I had tested it on that case.
I fixed it now. Thanks.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
htt
I expect to be able to get to any customization group by starting from
M-x customize RET and following the links. Groups that indeed don't
belong to any parent groups except `emacs' SHOULD have :group 'emacs.
I don't see what the problem is.
It is not right for these to be first-l
> In <[EMAIL PROTECTED]> Richard Stallman wrote:
> I got many warnings when compiling Gnus. For instance:
> smime.el:123:1:Warning: defgroup for `smime' fails to specify containing
> group
> I think that is a real bug. This group should surely be put in
> a logical place in the hi
I got many warnings when compiling Gnus. For instance:
smime.el:123:1:Warning: defgroup for `smime' fails to specify containing
group
I think that is a real bug. This group should surely be put in
a logical place in the hierarchy.
I think there might be customization groups which
Katsumi Yamaoka <[EMAIL PROTECTED]> writes:
> I think there might be customization groups which don't belong to
> any parent groups except `emacs'. Although it is possible to avoid
> warnings by adding the ``:group 'emacs'' parameters, I don't think
> it is useful especially for `defgroup'.
I ex
> In <[EMAIL PROTECTED]> Richard Stallman wrote:
> While cleaning up etc/NEWS I was reminded that the feature
> if the default group in defcustom is new in this release.
> I have never been happy with this default, and the best time
> to change things is now, before we make a release with it.
