[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: new compile command doesn't coalesce errors on the same line

From: Daniel Pfeiffer
Subject: Re: new compile command doesn't coalesce errors on the same line
Date: Wed, 17 Mar 2004 21:52:08 +0100


Miles Bader <address@hidden> skribis:

> If *compilation* looks like this:
> cray.c:33: error: `driver_num' undeclared (first use in this function)
> cray.c:33: error: (Each undeclared identifier is reported only once
> cray.c:33: error: for each function it appears in.)
> cray.c:36: error: too many arguments to function `make_driver'
> Then the first next-error jumps to (having working around the problems
> with next-error described in my previous mail) line 33.
> However, the next 2 invocations of `M-x next-error' _also_ jump to line
> 33, which is obvious a bit of a pain (since multi-line error messages
> like that are common from gcc).  The old compile command simply ignored
> any error lines which were duplicates.

compilation-skip-visited is your friend.  I chose not to default this to true,
because these may be several errors, and somebody might oversee that there was

coralament / best Grötens / liebe Grüße / best regards / elkorajn salutojn
Daniel Pfeiffer

P.S.: gnu.org is bouncing my mails.  If this doesn't show up on the list,
could you please forward it?

lerne / learn / apprends / läramå / ucz się    Esperanto:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]