From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Problems due to grep.el introduction
Date: 24 Jun 2004 13:26:50 +0200 [thread overview]
Message-ID: <m34qp18adh.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <2914-Wed23Jun2004215530+0300-eliz@gnu.org>
"Eli Zaretskii" <eliz@gnu.org> writes:
> Since the `grep' command and related functions are now on a separate
> file grep.el, unbundled Lisp packages that used `grep'-related
> features will become broken if they require `compile' and rely on
> `grep'-related variables and functions to become defined as a result.
> Moreover, the fact that grep.el was added is not even mentioned in
> NEWS, AFAICS.
>
> (I bumped into this when I installed ID-utils on a machine with a
> relatively recent CVS snapshot of Emacs, and found that "M-x gid"
> barfs becaise grep-regex-alist is not defined.)
>
> We definitely should mention grep.el in NEWS,
I didn't think it would cause problems which is why I didn't document
it. But it's not that trivial...
If some external package uses grep and does (require 'compile),
it is not sufficient just to change that into (require 'grep),
as that would break compatibility with pre 21.4 emacs which doesn't
have grep.el
For 21.4, the simplest fix would be to add (require 'grep)
at the end of compile.el -- after (provide 'compile).
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2004-06-24 11:26 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
2004-06-25 17:08 ` Eli Zaretskii
2004-07-03 11:05 ` Eli Zaretskii
2004-06-24 11:26 ` Kim F. Storm [this message]
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=m34qp18adh.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@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.