From: Miles Bader <miles@gnu.org>
Cc: miles@lsi.nec.co.jp, miles@gnu.org, emacs-devel@gnu.org,
rms@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: new compile command doesn't coalesce errors on the same line
Date: Sat, 20 Mar 2004 03:26:16 -0500 [thread overview]
Message-ID: <20040320082616.GA11718@fencepost> (raw)
In-Reply-To: <20040320074137.2ea2c886.occitan@esperanto.org>
On Sat, Mar 20, 2004 at 07:41:37AM +0100, Daniel Pfeiffer wrote:
> > Meanwhile, to the extent I can figure it out, I think this is indeed
> > something else. Let's just change the code so as to treat
> > contiguous errors as one.
>
> How contiguous do they have to be? How many lines apart may they be? Keep
> this in mind: Where the old compile was bound to line-beginnings, the new
> one can match a location anywhere on a line, even several different kinds
> on the same line as in
>
> What would we gain? Why would I want to go to the same spot again if it is
> mentioned 3 lines down, but not when it is mentioned on the next line?
It has to _at least_ handle correctly the cases the old compile command did.
Geez, I'm beginning to think it would be easier just to put the old one back.
-Miles
--
`Life is a boundless sea of bitterness'
next prev parent reply other threads:[~2004-03-20 8:26 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 [this message]
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
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
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=20040320082616.GA11718@fencepost \
--to=miles@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=miles@lsi.nec.co.jp \
--cc=monnier@iro.umontreal.ca \
--cc=rms@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).