all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: william.a.george@gmail.com
Subject: Re: Parsing compilation error/warning not possible.
Date: 19 Dec 2006 12:38:04 -0800	[thread overview]
Message-ID: <1166560684.889573.69150@80g2000cwy.googlegroups.com> (raw)
In-Reply-To: <1166555911.178767.309200@n67g2000cwd.googlegroups.com>


Robert Thorpe skrev:

> william.a.george@gmail.com wrote:
> > Hi.
> > I'm using Emacs on WindowsXP.
> > I make compilations through emacs with an own written Makefile. The
> > compilation result is presented on a new buffer. It should be possible
> > to click on the error or warning message to go directly to the
> > corresponding line in the file where the error is.
> > But I can't make it happen. I have read a little bit about this, and
> > what I could find is something about (compilation-error-regexp-alist)
> > that should fix this in someway.
> > Can anyone tell me how this should be done?
>
> Generally you do M-x compile
> Then enter the command to make the program, eg "make"
> Then you can select the errors one at a time by pressing C-x `
>
> This will only work if your compiler emits messages in a format
> understood by Emacs compile-mode.

Thanks for your response.
The compilation part is OK. The problem is that it is not possible to
select the errors in any way. Not by C-x or clicking mouse 2 button or
any other way.
The question is if my compiler is emitting messages in a format that is
understood by emacs compile-mode, as you said.
How can I make the compile-mode to understand my compiler messages?

  reply	other threads:[~2006-12-19 20:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-19 12:36 Parsing compilation error/warning not possible william.a.george
2006-12-19 19:18 ` Robert Thorpe
2006-12-19 20:38   ` william.a.george [this message]
2006-12-20  8:58     ` william.a.george
2006-12-20 18:54       ` Robert Thorpe
2006-12-22 11:53         ` william.a.george

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=1166560684.889573.69150@80g2000cwy.googlegroups.com \
    --to=william.a.george@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.
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.