From: Eli Zaretskii <eliz@gnu.org>
To: David Engster <deng@randomsample.de>
Cc: 14411@debbugs.gnu.org
Subject: bug#14411: 24.3.50; compile.el: Better file search for parallel builds
Date: Thu, 16 May 2013 22:19:48 +0300 [thread overview]
Message-ID: <83r4h6spez.fsf@gnu.org> (raw)
In-Reply-To: <87d2sqzqq5.fsf@engster.org>
> From: David Engster <deng@randomsample.de>
> Date: Thu, 16 May 2013 21:09:38 +0200
>
> When doing parallel builds using GNU Make, jumping to the location of a
> warning/error from the compilation buffer often does not work. This is
> because GNU Make enters different directories at the same time, and the
> resulting output is intermixed. The attached patch fixes this by looking
> at all directories which were entered up to the point of the
> warning/error, instead of just taking the directly preceding one. I'm
> aware that this is not a perfect solution, since those directories might
> contain files with identical names, in which case Emacs might show the
> wrong one, but IMO it's still an improvement over the current
> situation. This feature can also be disabled through a new variable.
I think this problem should be fixed in GNU Make. And, lo and behold,
the next release of GNU Make will have a switch that will prevent the
directories from being mixed. Perhaps it would be better to teach
compile.el to detect support for that switch (-O or --output-sync) and
use it if available when -j is also used, than to kludge around the
current behavior.
next prev parent reply other threads:[~2013-05-16 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 19:09 bug#14411: 24.3.50; compile.el: Better file search for parallel builds David Engster
2013-05-16 19:19 ` Eli Zaretskii [this message]
2020-09-18 14:35 ` Lars Ingebrigtsen
2020-09-18 15:36 ` Eli Zaretskii
2020-09-18 15:39 ` Lars Ingebrigtsen
2020-10-15 14:49 ` Lars Ingebrigtsen
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=83r4h6spez.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14411@debbugs.gnu.org \
--cc=deng@randomsample.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 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).