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: Fri, 04 Jun 2004 02:42:36 +0300	[thread overview]
Message-ID: <877juoqesz.fsf@mail.jurta.org> (raw)
In-Reply-To: <E1BTstf-0004im-60@fencepost.gnu.org> (Richard Stallman's message of "Fri, 28 May 2004 21:44:27 -0400")

Richard Stallman <rms@gnu.org> writes:
>     goto-error: C-m, C-c C-c, M-o
>
> Why do we want to define M-o as well as the other two?
> That doesn't follow any general convention, it isn't more
> convenient than C-m, and it isn't needed for compatibility.

Occur mode binds "o" to `occur-mode-goto-occurrence-other-window' and
diff mode binds "o" to `diff-goto-source'.  But since "o" should insert
the ?o character in other modes, I added "M-" key prefix.  Though,
M-o is not needed too much.

>     next-error-no-visit: M-n
>
> Let's call that forward-error-message.
>
>     previous-error-no-visit: M-p
>
> Let's call that backward-error-message.

So as I understand, a general convention would be using forward-/backward-
prefix for commands that move the point only in the current compile/grep/...
buffer, and next-/previous- for commands which are invoked in the
source buffers.  It would be good if this convention will be followed
for all function names.

>     next-error-file-no-select: M-}, M-N
>
> I'd rather avoid defining M-N and M-P as different from M-n and M-p.
> We don't need to do it; M-{ and M-} are equally easy to type.

They are not easy to type on most European keyboards, so alternative
keybindings couldn't hurt.

BTW, C-x ` is not easy to type on these keyboards too.  There could be
an alternative keybinding.

> Also, let's call these commands forward-error-source-file
> and backward-error-source-file.
>
>     next-error-file: new global command without keybindings
>     previous-error-file: new global command without keybindings
>
> What would these new commands do?

These commands would do the same what `forward-error-source-file' and 
backward-error-source-file' will do in the current compilation buffer.
But `next-error-file' and `previous-error-file' will be called
from the source buffers, like `next-error' and `previous-error',
and will visit the next file instead of the next error.

Actually, instead of adding these new commands it would be better
if `next-error' interpreted a special prefix argument with the
meaning to skip to the next file.  But it seems all possible prefix
arguments of C-x ` are already used.

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

  parent reply	other threads:[~2004-06-03 23:42 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           ` 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     ` Juri Linkov [this message]
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=877juoqesz.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).