unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: kl.vanw@gmail.com
Subject: Re: opening correct source file on compile error
Date: 24 Oct 2006 07:10:46 -0700	[thread overview]
Message-ID: <1161699046.662015.226520@m7g2000cwm.googlegroups.com> (raw)
In-Reply-To: <871woxubix.fsf@gmail.com>


Burton Samograd wrote:
> kl.vanw@gmail.com writes:
>
> > Kevin Rodgers wrote:
> >> kl.vanw@gmail.com wrote:
> >> > Kevin Rodgers wrote:
> >> >> kl.vanw@gmail.com wrote:
> >> >>> Here's my situation. My header files (C++) are located in a dir named
> >> >>> src/lib. These are the files I edit and are CVS managed. When I run
> >> >>> 'make', make copies the headers into include/, which my other source
> >> >>> files include. Then if there was an error in one of the headers, and I
> >> >>> use 'next-error' in the compilation buffer to open the header, emacs
> >> >>> opens the file in the include/ directory, but I really need it to open
> >> >>> the header in src/lib. Can I some how help emacs find the right
> >> >>> file?
>
> Might variable this help?  I was having a similar problem and this
> fixed it right up.
>
> compilation-search-path Variable:
>
> *List of directories to search for  source files named in error
> messages.
>

That certainly sounds like what I need, but it doesn't work for me. I
think I've spent too much time on the minor annoyance. Thanks for your
help.

--
Kevin

  reply	other threads:[~2006-10-24 14:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18 16:08 opening correct source file on compile error kl.vanw
2006-10-19 16:14 ` Kevin Rodgers
     [not found] ` <mailman.98.1161274520.2130.help-gnu-emacs@gnu.org>
2006-10-20 14:00   ` kl.vanw
2006-10-23 16:15     ` Kevin Rodgers
     [not found]     ` <mailman.162.1161620177.27805.help-gnu-emacs@gnu.org>
2006-10-24 12:04       ` kl.vanw
2006-10-24 12:46         ` Burton Samograd
2006-10-24 14:10           ` kl.vanw [this message]
2006-10-24 22:31             ` Burton Samograd
2006-10-24 21:53         ` Kevin Rodgers
     [not found]         ` <mailman.216.1161726966.27805.help-gnu-emacs@gnu.org>
2006-10-25 11:41           ` kl.vanw
2006-10-23 17:29   ` Ushnish Basu
2006-10-23 20:07     ` Kevin Rodgers
     [not found]     ` <mailman.175.1161634161.27805.help-gnu-emacs@gnu.org>
2006-10-23 22:23       ` Ushnish Basu

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=1161699046.662015.226520@m7g2000cwm.googlegroups.com \
    --to=kl.vanw@gmail.com \
    /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).