From: David Kastrup <dak@gnu.org>
Cc: miles@lsi.nec.co.jp, miles@gnu.org, rms@gnu.org,
monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: new compile command doesn't coalesce errors on the same line
Date: 29 Mar 2004 00:00:39 +0200 [thread overview]
Message-ID: <x5r7vcocmw.fsf@lola.goethe.zz> (raw)
In-Reply-To: <20040328233217.71d75077.occitan@esperanto.org>
dapfy@t-online.de (Daniel Pfeiffer) writes:
> Richard Stallman <rms@gnu.org> skribis:
>
> > > What if I then type C-x `? Will it got to the following error,
> > > or will it move down until it finds an error I have not yet visited?
> >
> > That is exactly the distinction made by the compilation-skip-visited
> > option. You can have one behaviour or the other.
> >
> > Now I understand. The doc string was not clear to me.
> >
> > I am now certain that setting compilation-skip-visited to t is NOT the
> > right way to handle consecutive errors on one source line. It has
> > other effects that I would not want.
> >
> > So compilation-skip-visited's default should remain nil,
> > but we need another feature to recognize consecutive error messages
> > on a single source line and disregard all but the first of them.
> >
> > Would you please implement that feature? There could be an
> > option to disable it.
>
> Sure, but I'm still not clear on what contiguous should mean. What if there
> are ten contiguous mentions of a location, but the *compilation* window is
> only five lines high?
Make it larger temporarily. That's what happens to the minibuffer in
similar cases. Of course I have no idea how to achieve that.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2004-03-28 22:00 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x5r7vcocmw.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=miles@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 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.