unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Glenn Morris <rgm@gnu.org>
Cc: 15795-done@debbugs.gnu.org
Subject: bug#15795: 24.3.50; Compile uses relative filenames, breaks goto next error.
Date: Fri, 04 Jul 2014 12:33:30 +0200	[thread overview]
Message-ID: <53B682FA.30805@swipnet.se> (raw)
In-Reply-To: <D4C1EB41-7461-442F-A10D-0FAE1BDFE655@swipnet.se>

Hello.

2013-11-04 19:34, Jan Djärv skrev:
> Hello.
>
> 4 nov 2013 kl. 09:10 skrev Glenn Morris <rgm@gnu.org>:
>
>>
>> PS try configuring your out-of-tree build using an absolute path to the
>> srcdir.
>
> That workaround works.

After I finally got round to do some debugging, I find that compile-mode does 
directory tracking, but for English only.  After setting up 
compilation-directory-matcher to handle my locale and english, everything 
works as expected.  Closing this bug.

For future reference, one might consider popping up a warning and a pointer to 
compilation-directory-matcher if the file is not found and directory tracking 
did not track a single directory.  Or use a more general regexp (don't know if 
that is possible), or force the C locale, or convice GNU make to add a 
specific switch, much like GNU ls has --dired.

Come to think of it, if doing parallel make where each job goes into separate 
directories, directory tracking will most likely fail, as output from 
different jobs are intermixed.  So directory tracking is not robust.

	Jan D.






  reply	other threads:[~2014-07-04 10:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-03  9:27 bug#15795: 24.3.50; Compile uses relative filenames, breaks goto next error Jan Djärv
2013-11-03 18:51 ` Glenn Morris
2013-11-04  8:10   ` Glenn Morris
2013-11-04 18:34     ` Jan Djärv
2014-07-04 10:33       ` Jan Djärv [this message]
2014-07-04 18:24         ` Glenn Morris
2014-07-04 18:38           ` David Engster

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=53B682FA.30805@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=15795-done@debbugs.gnu.org \
    --cc=rgm@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).