all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: byte-compile-nogroup-warn effectively disabled
Date: Sun, 08 Jun 2008 21:55:29 -0400	[thread overview]
Message-ID: <jwvzlpvz84k.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1K5T1i-0003CO-Jm@fencepost.gnu.org> (Richard M. Stallman's message of "Sun, 08 Jun 2008 18:06:14 -0400")

> This change
>      ;; Warn if a custom definition fails to specify :group.
>      (defun byte-compile-nogroup-warn (form)

>     +  (if (and (memq (car form) '(custom-declare-face custom-declare-variable))
>     +           byte-compile-current-group)
>     +      ;; The group will be provided implicitly.
>     +      nil

> effectively defeats the point of that warning, which is to
> make sure that every defcustom and defface specifies the group.

I know it's your opinion, and I disagree.  Even without an
explicit :group, the defcustom will have a proper group attributed to it
because it will use the last group defined in the file.  So, in my
opinion it fixes the warning so that it only occurs in cases where the
lack of the :group really leads to the variable being associated to no
group at all.


        Stefan




  reply	other threads:[~2008-06-09  1:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-08 22:06 byte-compile-nogroup-warn effectively disabled Richard M Stallman
2008-06-09  1:55 ` Stefan Monnier [this message]
2008-06-09  6:46   ` Drew Adams
2008-06-09  8:02     ` Stephen J. Turnbull
2008-06-09 13:55       ` Drew Adams
2008-06-09 20:09         ` Stephen J. Turnbull
2008-06-09 20:26           ` Drew Adams
2008-06-09 17:22     ` Richard M Stallman
2008-06-10  1:17       ` Stefan Monnier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvzlpvz84k.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.