all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: 7783@debbugs.gnu.org
Subject: bug#7783: 24.0.50; (elisp) autoloading nodes, autoload cookie	fordefine-globalized-minor-mode,...
Date: Wed, 5 Jan 2011 10:31:19 -0800	[thread overview]
Message-ID: <A9EFB284E12E4897BACE51326CCC8E73@us.oracle.com> (raw)
In-Reply-To: <83sjx7mgxl.fsf@gnu.org>

> > > What about `define-globalized-minor-mode'?  If that is not handled
> > > similarly, then that is a code bug - it should be.  If it 
> > > is handled similarly by a cookie then it should be included in
> > > the doc list.  Users should not need to consult the source code
> > > to try to determine what an autoload cookie before
> > > `define-globalized-minor-mode' will do.
> > 
> > Likewise `define-widget' and any others.  In sum the list 
> > in the manual should be complete, so users need not guess what
> > gets handled by an autoload cookie and what does not.
> 
> The text sounds as if the list is exhaustive, so the only issue is
> whether it is correct or not.

Sounds as if...maybe...sort of...depending on the reader.  I agree that that is
suggested.  But it would be clearer if we said explicitly that this is a
complete list.

But yes, my main concern is that the list be up-to-date (complete).






  reply	other threads:[~2011-01-05 18:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-04 21:34 bug#7783: 24.0.50; (elisp) autoloading nodes, autoload cookie for define-globalized-minor-mode, Drew Adams
2011-01-04 23:03 ` bug#7783: 24.0.50; (elisp) autoloading nodes, autoload cookie fordefine-globalized-minor-mode, Drew Adams
2011-01-05 16:52   ` Eli Zaretskii
2011-01-05 18:31     ` Drew Adams [this message]
2011-01-05 16:49 ` bug#7783: 24.0.50; (elisp) autoloading nodes, autoload cookie for define-globalized-minor-mode, Eli Zaretskii
2011-01-05 18:31   ` Drew Adams
2012-03-10  4:02 ` Chong Yidong

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=A9EFB284E12E4897BACE51326CCC8E73@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=7783@debbugs.gnu.org \
    --cc=eliz@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.