From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: schwab@suse.de, emacs-devel@gnu.org
Subject: Re: Problems due to grep.el introduction
Date: Thu, 24 Jun 2004 14:14:15 -0500 (CDT) [thread overview]
Message-ID: <200406241914.i5OJEFs18716@raven.dms.auburn.edu> (raw)
In-Reply-To: <2719-Thu24Jun2004212618+0300-eliz@gnu.org>
Eli Zaretskii wrote:
> From: Andreas Schwab <schwab@suse.de>
> Date: Thu, 24 Jun 2004 10:51:03 +0200
>
> > (autoload 'grep-regex-alist "grep")
> >
> > Comments?
>
> autoload doesn't work with variables.
So maybe the example was bad, but the original question still stands:
should we do that for some grep-* functions that were previously in
compile?
Why not just use autoload cookies in grep.el, rather than adding
autoloads to compile.el? Those _do_ work for variables and many
functions and some user options in grep.el already have autoload
cookies. Otherwise, the autoloads you add to compile.el will
eventually be duplicated in grep.el _anyway_. For instance, that is
what wound up happening to 34 of the 38 similar "dired-aux autoloads"
in dired.el. That caused plenty of trouble because the autoloads in
dired.el never got updated, resulting in obsolete docstrings being
displayed and the like. I recently removed all 38 "dired-aux
autoloads" in dired and added 4 autoload cookies to dired-aux.
Sincerely,
Luc.
next prev parent reply other threads:[~2004-06-24 19:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 19:55 Problems due to grep.el introduction Eli Zaretskii
2004-06-24 8:51 ` Andreas Schwab
2004-06-24 19:26 ` Eli Zaretskii
2004-06-24 19:14 ` Luc Teirlinck [this message]
2004-06-25 17:08 ` Eli Zaretskii
2004-07-03 11:05 ` Eli Zaretskii
2004-06-24 11:26 ` Kim F. Storm
2004-06-24 19:27 ` Eli Zaretskii
2004-06-24 21:40 ` Kim F. Storm
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=200406241914.i5OJEFs18716@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=emacs-devel@gnu.org \
--cc=schwab@suse.de \
/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.