From: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: next-error-last-buffer
Date: Wed, 12 May 2004 09:50:34 -0400 [thread overview]
Message-ID: <4n7jvhg3f9.fsf@lifelogs.com> (raw)
In-Reply-To: <87hdumto1j.fsf@mail.jurta.org> (Juri Linkov's message of "Wed, 12 May 2004 02:46:48 +0300")
On Wed, 12 May 2004, juri@jurta.org wrote:
> The current implementation of next-error framework is general enough
> to allow implementing different approaches easily (for example, I
> was able to implement the desired behavior with only one small
> change in the `next-error' function), but it is still not extensible
> enough.
>
> Based on my recent experience, I want to make some suggestions
> how to make it more extensible:
>
> 1. Add an option to allow the user to select among predefined
> behaviors. Though, this will not help the user if he will not
> find a desired option in the predefined set.
What predefined behaviors should we allow?
- use the last visited buffer
- prefer {compile,grep,occur} buffers
- use the visible buffers
- user-defined function
The behavior preferences should be in a list, so the user can say "use
my function, then use the visible buffers first, then try a compile
buffer, then use the last visited buffer" for instance. I really
think most users will be happy with a default of "last visited buffer"
but we should let the users decide by making it easy to configure.
> 2. Add a new user variable `next-error-find-buffer-function' and try
> to call it (i.e. to call it if it's fbound and return its value, but
> if it returns `nil', try other rules) in `next-error-find-buffer' at
> the top precedence level before all other rules. This will allow
> the user to override the standard rules for finding the next-error
> capable buffer with his own rule.
I think this should be just another behavior, not an overriding
preference. It could go in the middle of the search rules, for
instance.
> 3. Add a hook to `next-error' after the `funcall
> next-error-function' to allow the user to perform actions (such as
> setting buffer-local variables) in the buffer found by
> `next-error-function'.
I'm OK with that.
> I thought again about why the current behavior is too confusing
> and I think I found the reason: the most confusing is the fact that
> the compilation buffer is visible in the window adjacent to the
> source file window where the point is located, but typing C-x `
> uses the last but not visible compilation buffer.
You are not a typical user. I, for instance, have NEVER run more than
one compilation at a time. I may have to in the future, sure, but I
doubt it's typical user behavior.
> So w.r.t. `next-error-find-buffer' I propose to modify it to use the
> following priority order:
>
> 1(new). Try to call a user-defined
> `next-error-find-buffer-function'. 2. If the current buffer is a
> next-error capable buffer, return it. 3(new). If a next-error
> capable buffer is in one of the windows of the current frame, return
> it. 4. If next-error-last-buffer is set to a live buffer, use that.
> 5. Otherwise, look for a next-error capable buffer 6. Signal an
> error if there are none.
I think the current buffer should override any other rules. The
other rules' order should be user-configurable.
Ted
next prev parent reply other threads:[~2004-05-12 13:50 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 ` Ted Zlatanov [this message]
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 ` next-error-last-buffer Juri Linkov
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=4n7jvhg3f9.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).