all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: next-error
Date: Sun, 29 Aug 2004 23:37:56 +0300	[thread overview]
Message-ID: <87vff1wgln.fsf@mail.jurta.org> (raw)
In-Reply-To: <16683.28246.52467.757743@ihs.com> (Kevin Rodgers's message of "Tue, 24 Aug 2004 10:35:34 -0600")

Kevin Rodgers <ihs_4664@yahoo.com> writes:
> I maintain a small package that calls next-error, which in Emacs 21.3
> selected the source buffer in accordance with compilation-goto-locus's
> doc string:
>
> | Selects a window with point at SOURCE, with another window displaying ERROR.
>
> But a user reports that in CVS Emacs (specifically, the July 9 snapshot
> available at www.crasseux.com), next-error selects the *grep*
> compilation buffer instead of the source buffer.  Is that true, and is
> the change intentional?  If so, what is the right way to get the source
> buffer after calling next-error now?

I have some changes not yet installed in CVS (I will install them in
the next few days) and one of them is changing the rules for finding
the appropriate source buffer for `next-error'.  Perhaps, this change
will fix your problem.  Could you provide more details about this case?
>From what buffer do you call `next-error'?  What was the command that
produced the last next-error capable buffer?  Maybe, you need to
change the rules in the `next-error-find-buffer' function?

-- 
Juri Linkov
http://www.jurta.org/emacs/

  reply	other threads:[~2004-08-29 20:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 16:35 next-error Kevin Rodgers
2004-08-29 20:37 ` Juri Linkov [this message]
2004-08-31 22:49   ` next-error Kevin Rodgers

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=87vff1wgln.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=emacs-devel@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.