From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Markus Rost <rost@mathematik.uni-bielefeld.de>,
emacs-devel@gnu.org, occitan@esperanto.org
Subject: Re: compilation-forget-errors still used by tex-mode.el
Date: 19 Mar 2004 09:25:39 -0500 [thread overview]
Message-ID: <jwvwu5g9apa.fsf-monnier+emacs@asado.iro.umontreal.ca> (raw)
In-Reply-To: <m3ish1i0t6.fsf@kfs-l.imdomain.dk>
> There should be commands for both, e.g. C-x ` (next-error) takes next
> error independently of point, while some other command (I'd prefer
> RET, but that's another, old, discussion) takes you to the error on the
> current line (or next error following it (and moves next-error marker
> accordingly).
There's already M-RET (or something like that: compilation-goto-error,
together with the mouse version compilation-mouse-goto-error).
>> My current patch basically reproduces the behavior of the old code:
>> it re-introduces `compilation-parsing-end' and uses it as the "current
>> error" marker. While I think that using a marker is the best option and
>> that re-introducing `compilation-parsing-end' for compatibility purposes is
>> right as well, I'm not convinced that merging the two is such a hot idea.
>> We should maybe just introduce a new `compilation-current-error' marker
>> instead and keep `compilation-parsing-end' for compatibility only.
> And add compilation-current-error to overlay-arrow-variable-list :-)
Now there's an idea.
Stefan
next prev parent reply other threads:[~2004-03-19 14:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1B1se8-0003lr-00@yui26.Mathematik.Uni-Bielefeld.DE>
[not found] ` <jwvwu5p6949.fsf-monnier+emacs@asado.iro.umontreal.ca>
[not found] ` <jwvsmg6rm15.fsf-monnier+emacs@asado.iro.umontreal.ca>
[not found] ` <E1B43eN-0003F5-00@yui26.Mathematik.Uni-Bielefeld.DE>
[not found] ` <jwvn06dsy2i.fsf-monnier+emacs@asado.iro.umontreal.ca>
[not found] ` <E1B44qZ-0003Yp-00@yui26.Mathematik.Uni-Bielefeld.DE>
[not found] ` <jwvbrmtsup7.fsf-monnier+emacs@asado.iro.umontreal.ca>
[not found] ` <E1B45ij-0003ni-00@yui26.Mathematik.Uni-Bielefeld.DE>
[not found] ` <jwv1xnpsru8.fsf-monnier+emacs@asado.iro.umontreal.ca>
[not found] ` <E1B46gC-0004BN-00@yui26.Mathematik.Uni-Bielefeld.DE>
2004-03-19 5:51 ` compilation-forget-errors still used by tex-mode.el Stefan Monnier
2004-03-19 10:33 ` Kim F. Storm
2004-03-19 14:25 ` Stefan Monnier [this message]
2004-03-19 21:41 ` Miles Bader
2004-03-20 17:01 ` Markus Rost
2004-03-20 19:41 ` Daniel Pfeiffer
2004-03-21 0:14 ` Markus Rost
2004-03-31 11:57 ` Daniel Pfeiffer
2004-04-01 13:13 ` Kim F. Storm
2004-04-01 16:18 ` monnier
2004-04-01 18:34 ` Daniel Pfeiffer
2004-04-01 21:34 ` Kim F. Storm
2004-04-02 2:01 ` Miles Bader
2004-04-02 11:07 ` Kim F. Storm
2004-04-02 16:10 ` Daniel Pfeiffer
2004-04-02 16:19 ` Stefan Monnier
2004-04-02 19:28 ` Kim F. Storm
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=jwvwu5g9apa.fsf-monnier+emacs@asado.iro.umontreal.ca \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=occitan@esperanto.org \
--cc=rost@mathematik.uni-bielefeld.de \
/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).