From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: compile.el
Date: Tue, 23 Aug 2005 22:33:48 +0300 [thread overview]
Message-ID: <87oe7oe9mz.fsf@jurta.org> (raw)
In-Reply-To: <E1E7I5A-0007Nl-Li@fencepost.gnu.org> (Richard M. Stallman's message of "Mon, 22 Aug 2005 15:35:44 -0400")
> My patch to compile.el has a bug; here's a revised patch.
It has another bug: visiting a saved compilation/grep file fails with
the error message:
Symbol's value as variable is void: comint-file-name-prefix
This is trivial to fix - just restore `(boundp 'comint-file-name-prefix)'
that was there before the patch. But it has another more severe bug:
visiting a file in a compilation subdirectory extracted from the line
`make: Entering directory ...' doesn't work anymore.
Since the issue of visiting saved compilation/grep logs is currently
under consideration, I want also to point out that changing the file's
default directory by the -*- line is not a good thing. It is
potentially dangerous when an unsuspecting user assumes that the
default directory is the same as the directory where the file
is saved, but actually it changes to the directory where compilation
was started. I think `-*- default-directory: "..." -*-' in the first
line should be changed to `-*- compilation-directory: "..." -*-'.
Currently this doesn't work with `compilation-directory' in the first
line, but it is easy to fix compile.el to take into account this case.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2005-08-23 19:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 19:35 compile.el Richard M. Stallman
2005-08-23 19:33 ` Juri Linkov [this message]
2005-09-09 2:24 ` compile.el Richard M. Stallman
2005-09-09 6:28 ` compile.el Juri Linkov
2005-09-09 12:50 ` compile.el Richard M. Stallman
2005-09-09 14:57 ` compile.el Juri Linkov
2005-09-10 8:14 ` compile.el Richard M. Stallman
2005-09-10 9:15 ` compile.el Juri Linkov
2005-09-09 2:24 ` compile.el Richard M. Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oe7oe9mz.fsf@jurta.org \
--to=juri@jurta.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).