unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: next-error-last-buffer
Date: Sat, 29 May 2004 00:07:46 +0300	[thread overview]
Message-ID: <87n03sfd1x.fsf@mail.jurta.org> (raw)
In-Reply-To: <4nu0y0ef4z.fsf@lifelogs.com> (Ted Zlatanov's message of "Fri, 28 May 2004 11:38:04 -0400")

Ted Zlatanov <tzz@lifelogs.com> writes:
> Let me make sure I understand the problem and solution.
>
> When next-error is called in buffer X, it may pop the user into
> buffer Y.  We want to unset next-error-function in Y, so that
> next-error does not act in Y from that point on.

Correct.

> Couldn't this be achieved by making the next-error-last-buffer check
> in next-error-find-buffer precede the current-buffer check?

This change will solve the problem.

> We need to define a function next-error-follow-this-buffer that would
> set next-error-last-buffer to (current-buffer).  That way, users can
> force the behavior that now is the default, that next-error should act
> on (current-buffer) first and foremost.  I would bind
> next-error-follow-this-buffer to C-x ~ (which on US keyboards is
> Shift-` so remembering it is not too bad).

There is no need for an additional function and keybinding.  The action
you proposed (i.e. setting next-error-last-buffer to (current-buffer))
could be performed in location-visiting functions usually bound to C-m
and C-c C-c.

But there is even simpler solution for the user to select a buffer
for the next C-x `.

Taking into account the recent addition of a rule in
`next-error-find-buffer' which returns a buffer which is displayed
only in one window with a next-error capable buffer on the selected
frame, the user can simply remove the unwanted window with a
next-error capable buffer (e.g. *grep* buffer in the aforementioned
test case) from the selected frame and C-x ` will use the buffer from
the remaining window (e.g. a patch file) even if it is not the same as
next-error-last-buffer.

So the only change needed is to modify the rule order like you proposed,
which could look as below:

1. If one window on the selected frame displays such buffer, return it.
2. If next-error-last-buffer is set to a live buffer, use that.
3. If the current buffer is a next-error capable buffer, return it.
...

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

  reply	other threads:[~2004-05-28 21:07 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-09  0:44 next-error-last-buffer Juri Linkov
2004-05-09 18:47 ` next-error-last-buffer Richard Stallman
2004-05-09 23:32   ` next-error-last-buffer Juri Linkov
2004-05-10 17:54     ` next-error-last-buffer Richard Stallman
2004-05-10 18:28       ` next-error-last-buffer Stefan Monnier
2004-05-10 23:45         ` next-error-last-buffer Juri Linkov
2004-05-11 12:23           ` next-error-last-buffer Richard Stallman
2004-05-10 23:35       ` next-error-last-buffer Juri Linkov
2004-05-11  2:19         ` next-error-last-buffer Stefan Monnier
2004-05-11 15:36         ` next-error-last-buffer Ted Zlatanov
2004-05-11 23:46           ` next-error-last-buffer Juri Linkov
2004-05-12 13:50             ` next-error-last-buffer Ted Zlatanov
2004-05-13  4:15               ` next-error-last-buffer Juri Linkov
2004-05-13 13:01                 ` next-error-last-buffer Ted Zlatanov
2004-05-12 19:42             ` next-error-last-buffer Richard Stallman
2004-05-13  4:23               ` next-error-last-buffer Juri Linkov
2004-05-13  4:57                 ` next-error-last-buffer Miles Bader
2004-05-13  5:17                   ` next-error-last-buffer Stefan Monnier
2004-05-13  5:34                   ` next-error-last-buffer Juri Linkov
2004-05-13  7:28                     ` next-error-last-buffer Miles Bader
2004-05-13 12:54               ` next-error-last-buffer Ted Zlatanov
2004-05-14  9:21                 ` next-error-last-buffer Richard Stallman
2004-05-14 14:58                   ` next-error-last-buffer Ted Zlatanov
2004-05-15  8:21                     ` next-error-last-buffer Juri Linkov
2004-05-15 18:34                       ` next-error-last-buffer Richard Stallman
2004-05-15  8:53                     ` next-error-last-buffer Richard Stallman
2004-05-24  8:46 ` next-error-last-buffer Juri Linkov
2004-05-24 14:16   ` next-error-last-buffer Ted Zlatanov
2004-05-25 20:09     ` next-error-last-buffer Juri Linkov
2004-05-26 13:49       ` next-error-last-buffer Ted Zlatanov
2004-05-27 12:46       ` next-error-last-buffer Richard Stallman
2004-05-28 15:38         ` next-error-last-buffer Ted Zlatanov
2004-05-28 21:07           ` Juri Linkov [this message]
2004-05-29  3:47             ` next-error-last-buffer Ted Zlatanov
2004-05-30 14:30               ` next-error-last-buffer Richard Stallman
2004-06-01 17:41                 ` next-error-last-buffer Ted Zlatanov
2004-06-01 17:57                   ` next-error-last-buffer Ted Zlatanov
2004-06-02 17:36                     ` next-error-last-buffer Richard Stallman
2004-06-03 15:21                       ` next-error-last-buffer Ted Zlatanov
2004-06-04  2:03                         ` next-error-last-buffer Richard Stallman
2004-06-07 16:18                           ` next-error-last-buffer Ted Zlatanov
2004-06-08 20:31                             ` next-error-last-buffer Richard Stallman
2004-06-30 18:38                               ` next-error-last-buffer Ted Zlatanov
2004-07-01 17:14                                 ` next-error-last-buffer Richard Stallman
2004-05-25 16:06   ` next-error-last-buffer Richard Stallman
2004-05-25 20:14     ` next-error-last-buffer Juri Linkov
2004-05-26 13:56       ` next-error-last-buffer Ted Zlatanov
2004-05-27 21:55         ` next-error-last-buffer Juri Linkov
2004-05-27 23:53         ` next-error-last-buffer Richard Stallman
2004-05-28 15:29           ` next-error-last-buffer Stefan Monnier
2004-05-28 21:55             ` next-error-last-buffer Juri Linkov
2004-05-29  3:35             ` next-error-last-buffer Ted Zlatanov
2004-05-29 17:03             ` next-error-last-buffer Richard Stallman
2004-05-25 20:22 ` next-error-last-buffer Juri Linkov
2004-05-29  1:44   ` next-error-last-buffer Richard Stallman
2004-05-29 23:10     ` next-error-last-buffer Kim F. Storm
2004-05-30 19:41       ` next-error-last-buffer Richard Stallman
2004-05-31  6:39         ` next-error-last-buffer Werner LEMBERG
2004-05-31  7:20           ` next-error-last-buffer Juanma Barranquero
2004-06-01 17:52     ` next-error-last-buffer Ted Zlatanov
2004-06-01 21:33       ` next-error-last-buffer Kim F. Storm
2004-06-02 17:36       ` next-error-last-buffer Richard Stallman
2004-06-03 23:42     ` next-error-last-buffer Juri Linkov
2004-06-05 13:48       ` next-error-last-buffer Richard Stallman

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=87n03sfd1x.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 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).