From: Martin Fischer <nospam@nospam.net>
To: info-gnus-english@gnu.org
Subject: Re: Compilation mode; action when visiting next locus
Date: Tue, 18 Dec 2007 14:07:34 +0100 [thread overview]
Message-ID: <1063ywnobt.fsf@nospam.net> (raw)
In-Reply-To: <87odcp63za.fsf@paddy.ionicsoft.com>
>>>>> Arnaud Diederen (aundro) writes:
> Date: 17 Dec 2007 10:54:33 +0100
8<--------------------------------------------------------------------
>
> Actually, what I'd like is an "onvisitlocus" hook, if I may say
> so. ..and I have no idea how to that at all. Can anyone help?
>
Hi,
look at the documentation of the command next-error (M-x
apropos-command RET next-error RET) and you will be directed to
next-error-hook, which is what you are looking for.
Martin
--
parozusa at web dot de
next prev parent reply other threads:[~2007-12-18 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 9:54 Arnaud Diederen (aundro)
2007-12-18 11:47 ` Reiner Steib
2007-12-19 8:45 ` Arnaud Diederen (aundro)
2007-12-18 13:07 ` Martin Fischer [this message]
2007-12-19 8:46 ` Arnaud Diederen (aundro)
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=1063ywnobt.fsf@nospam.net \
--to=nospam@nospam.net \
--cc=info-gnus-english@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.
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 NNTP newsgroup(s).