From: glen stark <g.a.stark@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: emacs, jumping to relative file locations in compiler output.
Date: Thu, 27 Mar 2014 12:14:57 GMT [thread overview]
Message-ID: <5DUYu.30765$4k7.4511@fx31.am4> (raw)
In the company I'm working for, the build system is set up to cd in
various directories, and the call make. When a compiler error is
returned, it is of the form:
In file included from ../../../../include/whatever.h:33:0
emacs is then unable to determine where to look for the file in question.
Changing out build system is big project, but I'd like to be able to jump
around to compiler errors in emacs. In practice I know what path I
should substitute for "../../../../"
Is there someway I can tell emacs to regex substitute a fixed path for a
string of the form "../../"?
Is there an alternative solution to my problem (that doesn't mean
modifying the build system :) ).
Many thanks,
Glen
next reply other threads:[~2014-03-27 12:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 12:14 glen stark [this message]
2014-03-27 12:26 ` emacs, jumping to relative file locations in compiler output glen stark
2014-03-27 16:13 ` Pascal J. Bourguignon
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='5DUYu.30765$4k7.4511@fx31.am4' \
--to=g.a.stark@gmail.com \
--cc=help-gnu-emacs@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.
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).