From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: new compile command doesn't coalesce errors on the same line
Date: 29 Mar 2004 00:59:08 +0200 [thread overview]
Message-ID: <m31xncd1dv.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <20040328233217.71d75077.occitan@esperanto.org>
dapfy@t-online.de (Daniel Pfeiffer) writes:
> How about intervening lines, as a compiler at work gives me? Are these still
> contiguous:
>
> a.c:9: bla bla
> bla bla happened here:
> y = f( x );
> ^
> a.c:9: foo bar ...
IMHO, to keep things simple, I would say no.
>
> I guess we'd need to limit the height of a contiguous block to the (most
> recently) visible lines, and ignore anything else there is within that area.
All of this sounds overly complicated.
Can't it simply be done by saying that if two or more consecutive
lines points to the same source line, it shall ignore all but the first one.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2004-03-28 22:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 7:46 new compile command doesn't coalesce errors on the same line Miles Bader
2004-03-17 20:52 ` Daniel Pfeiffer
2004-03-17 22:47 ` Miles Bader
2004-03-17 23:04 ` Stefan Monnier
2004-03-19 18:12 ` Daniel Pfeiffer
2004-03-20 4:48 ` Richard Stallman
2004-03-20 6:41 ` Daniel Pfeiffer
2004-03-20 8:26 ` Miles Bader
2004-03-20 19:33 ` Daniel Pfeiffer
2004-03-21 19:21 ` Richard Stallman
2004-03-21 4:59 ` Richard Stallman
2004-03-21 4:59 ` Richard Stallman
2004-03-21 8:22 ` Daniel Pfeiffer
2004-03-22 5:24 ` Richard Stallman
2004-03-23 19:23 ` Daniel Pfeiffer
2004-03-25 2:00 ` Richard Stallman
2004-03-28 21:32 ` Daniel Pfeiffer
2004-03-28 21:39 ` Stefan Monnier
2004-03-28 22:00 ` David Kastrup
2004-03-28 22:59 ` Kim F. Storm [this message]
2004-03-29 20:56 ` Richard Stallman
2004-03-31 19:59 ` Daniel Pfeiffer
2004-03-17 23:16 ` Kim F. Storm
2004-03-17 20:58 ` Daniel Pfeiffer
2004-03-17 22:34 ` Miles Bader
2004-03-18 11:14 ` Andreas Schwab
2004-03-19 18:16 ` Daniel Pfeiffer
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=m31xncd1dv.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@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.
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.