unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
Subject: Re: next-error-last-buffer
Date: Tue, 25 May 2004 23:22:11 +0300	[thread overview]
Message-ID: <87d64sgsw9.fsf@mail.jurta.org> (raw)
In-Reply-To: <871xluig40.fsf@mail.jurta.org> (Juri Linkov's message of "Sun, 09 May 2004 03:44:31 +0300")

It seems more work is needed to generalize the next-error framework
for different modes.  The functions next-error-*, previous-error-*
is a good start, but there are still similar functions with different
names in compile/grep/occur/diff.  And what is worse is that all these
modes have different keybindings for similar functions.

Below is a proposal for unification of command names and keybindings.
On the first indentation level there is a new command name with
unified keybindings.  On the second level - mode map name.  On the
third level - the current keybinding and command name.

goto-error: C-m, C-c C-c, M-o
  compilation-mode-map
    C-c C-c  compile-goto-error
    C-m      compile-goto-error
  grep-mode-map
    \r       compile-goto-error
  diff-mode-shared-map
    C-M-m    diff-goto-source
    M-o      diff-goto-source
    C-c C-c  diff-goto-source
  occur-mode-map
    C-c C-c  occur-mode-goto-occurrence
    C-m      occur-mode-goto-occurrence

goto-error-no-select: C-o
  occur-mode-map
    o        occur-mode-goto-occurrence-other-window
    C-o      occur-mode-display-occurrence

next-error-no-visit: M-n
  compilation-mode-map
    M-n      compilation-next-error
  diff-mode-shared-map
    M-n      diff-hunk-next
  occur-mode-map
    M-n      occur-next

previous-error-no-visit: M-p
  compilation-mode-map
    M-p      compilation-previous-error
  diff-mode-shared-map
    M-p      diff-hunk-prev
  occur-mode-map
    M-p      occur-prev

next-error-no-select: C-M-n
  grep-mode-map
    n        next-error-no-select

previous-error-no-select: C-M-p
  grep-mode-map
    p        previous-error-no-select

next-error-file-no-select: M-}, M-N
  compilation-mode-map
    M-}      compilation-next-file
  grep-mode-map
    }        compilation-next-file
    \t       compilation-next-file
  diff-mode-shared-map
    M-N      diff-file-next
    M-}      diff-file-next

previous-error-file-no-select: M-{, M-P
  compilation-mode-map
    M-{      compilation-previous-file
  grep-mode-map
    {        compilation-previous-file
  diff-mode-shared-map
    M-P      diff-file-prev
    M-{      diff-file-prev

next-error-file: new global command without keybindings
previous-error-file: new global command without keybindings


Other current keybindings which could be unified somehow as well:

compilation-mode-map
    SPC      scroll-up
    DEL      scroll-down

grep-mode-map
    SPC      scroll-up
    DEL      scroll-down

diff-mode-shared-map
    M-SPC    scroll-up
    M-DEL    scroll-down
    M-q      quit-window

occur-mode-map
    r       occur-rename-buffer
    c       clone-buffer
    g       revert-buffer
    q       quit-window
    z       kill-this-buffer

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

  parent reply	other threads:[~2004-05-25 20:22 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 ` Juri Linkov [this message]
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=87d64sgsw9.fsf@mail.jurta.org \
    --to=juri@jurta.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).