unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: dapfy@t-online.de (Daniel Pfeiffer)
Cc: miles@lsi.nec.co.jp, emacs-devel@gnu.org,
	monnier@iro.umontreal.ca, miles@gnu.org
Subject: Re: new compile command doesn't coalesce errors on the same line
Date: Tue, 23 Mar 2004 20:23:59 +0100	[thread overview]
Message-ID: <20040323202359.1f75a72f.occitan@esperanto.org> (raw)
In-Reply-To: <E1B5HvK-00076I-Vj@fencepost.gnu.org>

Saluton, Moin,

Richard Stallman <rms@gnu.org> skribis:

>     *Compilation motion commands skip visited locations if this is t.
>     A location is considered visited if you've already jumped there.  It
>     doesn't matter if this happened from a different message.  After you
>     start a new compilation, all locations will again be initially
>     considered unvisited.
> 
> The condition is clear now.  I am not sure what "Compilation motion
> commands" are or what "skip" means.  Could you explain?

I believe I've inherited the term "Compilation motion commands" from the old
library.  They are the various next- or previous-error type of commands.

> What will happen if I move up in the compilation buffer and type RET
> to revisit an error I already saw?  Will it be "skipped"?

RET or mouse clicking is not motion in the above sense.  It tells Emacs "I
want to go to _this_ location" and that is of course always honoured.

> 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.

>     The example I cited
> 
>     location a: ... location b
>     location a: more bla about a
> 
>     is not contrived.  I've seen this frequently at work.  The old compile
>     simply ignored location b.  Now it is found and breaks immediate
>     contiguousness.
> 
> I see what you mean.  I don't have an opinion about it.
> I won't say this is a bad change.

This is only important if people want to be able to distinguish skipping
nearby mentions of the same location, but not far away ones.  I had called for
a vote on this a few days ago, and so far noone has come forward to say they
must have this distinction.

Then I'd say we stick with compilation-skip-visited's current behaviour.  We'd
just make it default to t as several people requested.

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

-- 
lerne / learn / apprends / läramå / ucz się    Esperanto:
                              http://lernu.net/

  reply	other threads:[~2004-03-23 19:23 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 [this message]
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=20040323202359.1f75a72f.occitan@esperanto.org \
    --to=dapfy@t-online.de \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=miles@lsi.nec.co.jp \
    --cc=monnier@iro.umontreal.ca \
    --cc=occitan@esperanto.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).