all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: compile.el
Date: Fri, 09 Sep 2005 09:28:44 +0300	[thread overview]
Message-ID: <87psriwy8z.fsf@jurta.org> (raw)
In-Reply-To: <E1EDYZE-0004lF-TB@fencepost.gnu.org> (Richard M. Stallman's message of "Thu, 08 Sep 2005 22:24:40 -0400")

>     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.
>
> Can you send me a precise test case for this?  Then I will debug it.

Find a file in one of the lisp subdirectories (e.g. `progmodes') that
produces a warning/error, or artificially cause a warning/error by
putting garbage in .el files.  Then at the top directory of Emacs
source tree, call `M-x compile' with the command:

make -C lisp EMACS=../src/emacs recompile

After that, trying to visit a file with warnings/errors from the line like

  In toplevel form:
  progmodes/grep.el:1:1:Warning: reference to free variable `foo'

doesn't find the location of `progmodes/grep.el'.

Without the patch you sent in one of the previous messages, compile.el
was able to extract the directory name from the string:

  make: Entering directory `{absolute directory of source tree}/emacs/lisp'

and use it even for files located in subdirectories of `emacs/lisp'.

-- 
Juri Linkov
http://www.jurta.org/emacs/

  reply	other threads:[~2005-09-09  6:28 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 ` compile.el Juri Linkov
2005-09-09  2:24   ` compile.el Richard M. Stallman
2005-09-09  6:28     ` Juri Linkov [this message]
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

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

  git send-email \
    --in-reply-to=87psriwy8z.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 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.