RE: [External] : Re: [ELPA] New package: dired-duplicates

[Drew Adams <drew.adams@oracle.com>]

> > > If a ‘defcustom’ does not specify any ‘:group’, the last group
> > > defined with ‘defgroup’ in the same file will be used.  This way,
> > > most ‘defcustom’ do not need an explicit ‘:group’.
> >
> > All true.
> > But "not need" doesn't imply "shouldn't have".
> 
> We decided that it means "shouldn't have".

I wasn't aware that such a rigid decision had been made.

However, I don't see it in the Elisp manual.  Where is
it specified?

Instead, in the Elisp manual, node `Group Definitions':

  you specify the group’s members by using the
  ‘:group’ keyword when defining those members.

Sounds a bit like one explicitly specifies :group
for each member.  Nothing about specifying it only
for the first member of a set of consecutive member
definitions.  Ambiguous, at best, I guess, if it's
intended to say where and when you "should" specify
:group.

Perhaps you should change the text quoted by Michael,
to make clear that you don't really mean (what most
people understand by) "do not need", but instead you
really mean "shouldn't have"?

  If a ‘defcustom’ does not specify any ‘:group’, the last group
  defined with ‘defgroup’ in the same file will be used.  This way,
  most ‘defcustom’ do not need an explicit ‘:group’.
                   ^^^^^^^^^^^
                 shouldn't have

As for an explicit statement of the convention, I
find nothing at all about :group in the sections
of the manual (such as `Coding Conventions'), that
state the Elisp coding conventions.

Is this a doc bug?  Is there somewhere else where
what you say was decided is declared?

> > > If :group is specified, it will most of the time mean
> > > the defcustom should be assigned to some other, not
> > > to the default, group.  So it's better style to not
> > > explicitly specify the default.
> >
> > FWIW, I disagree, stylistically; I think it's worse
> > style.
> 
> You are entitled to your opinions, but it is futile to reiterate them
> here, since the project as a whole has decided on a certain policy,
> and we ask you to please respect that and stop fighting it here, lest
> someone is mistaken to think that it is a matter of personal
> preferences, when Emacs source code is discussed.

I made clear that I was talking about use of :group by
users in their code, not for code that's to be included
in Emacs.  Very clear.  No fighting, though you appear
to be trying.

But I now have the question about where your edict about
:group is proclaimed for code that's to be included in
Emacs.  Where is that, besides in your slap-down reply
to my msg?