From: Benjamin Rutt <brutt+news@bloomington.in.us>
Cc: emacs-devel@gnu.org
Subject: Re: [patch] add interactive browse of revisions from vc *Annotate* buffers
Date: Mon, 12 Jan 2004 15:35:53 -0500 [thread overview]
Message-ID: <wc37jzw9a6u.fsf@mu.cis.ohio-state.edu> (raw)
In-Reply-To: 1073937837.2822.180.camel@localhost
Andre Spiegel <spiegel@gnu.org> writes:
> I like the features you (Benjamin) are suggesting but the keybindings
> seem a bit problematic to me. Since those features would be very
> important in VC Annotate, I wonder if you couldn't use simpler
> bindings. Ideally, I'd put the annotate buffer in view mode and use "p"
> and "n" for previous and next, but these are already bound to
> View-search-last-regexp-backward/forward. Do people think it's
> justified to replace that binding in vc-annotate-mode? I would think
> the relative importance justifies it. To annotate from the revision
> _before_ the one on the current line (which I feel is the most important
> of those new features), "f" could be used (similar to Dired), without
> any clash in view mode.
I'm not a view-mode user, so I can't give my opinion on how I'd feel
about those bindings being clobbered, but I do agree that simpler key
bindings will be better. Also, if we don't do something like derive
annotate-mode from view-mode, we should at least make the annotate
buffer read-only once it is built.
I like the idea of moving the "annotate the revision _before_ the one
on the current line" command away from being just invokable via a
prefix modifier of another command, to being a first-class citizen in
itself, invokable directly.
I don't care what actual keys are used myself, I'll let some others
give their opinions on that. I wouldn't have a problem with using
"p", "n" and "f" as you've described above.
--
Benjamin
next prev parent reply other threads:[~2004-01-12 20:35 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 2:54 [patch] add interactive browse of revisions from vc *Annotate* buffers Benjamin Rutt
2004-01-12 5:30 ` Andre Spiegel
2004-01-12 11:06 ` Kim F. Storm
2004-01-12 13:58 ` Benjamin Rutt
2004-01-12 17:11 ` Kim F. Storm
2004-01-12 17:20 ` Benjamin Rutt
2004-01-12 20:09 ` Andre Spiegel
2004-01-12 20:35 ` Benjamin Rutt [this message]
2004-01-13 10:57 ` Kim F. Storm
2004-01-14 15:45 ` Richard Stallman
2004-01-14 21:55 ` Kim F. Storm
2004-01-15 19:58 ` Andre Spiegel
2004-01-16 10:40 ` Richard Stallman
2004-01-16 16:30 ` Kim F. Storm
2004-01-17 12:55 ` Richard Stallman
2004-01-17 21:34 ` Benjamin Rutt
2004-01-19 13:33 ` Andre Spiegel
2004-01-19 20:39 ` Kai Grossjohann
2004-01-19 20:54 ` Benjamin Rutt
2004-01-20 1:28 ` Kim F. Storm
2004-01-20 15:31 ` Richard Stallman
2004-01-21 11:26 ` Kim F. Storm
2004-01-21 14:15 ` Stefan Monnier
2004-01-21 16:39 ` Kim F. Storm
2004-01-21 18:38 ` Stefan Monnier
2004-01-22 22:06 ` Kim F. Storm
2004-01-22 23:39 ` Andre Spiegel
2004-01-23 1:54 ` Benjamin Rutt
2004-01-22 19:00 ` Richard Stallman
2004-01-23 2:02 ` Miles Bader
2004-02-07 2:06 ` Kim F. Storm
2004-01-20 18:11 ` Kevin Rodgers
2004-01-20 15:32 ` Stefan Monnier
2004-01-20 16:45 ` Benjamin Rutt
2004-01-20 18:26 ` Stefan Monnier
2004-01-20 20:10 ` Benjamin Rutt
2004-01-19 21:13 ` Benjamin Rutt
2004-01-20 17:58 ` Andre Spiegel
2004-01-20 20:05 ` Benjamin Rutt
2004-01-20 20:33 ` Stefan Monnier
2004-01-20 22:28 ` Benjamin Rutt
2004-01-22 23:20 ` Kevin Rodgers
2004-01-22 23:40 ` Stefan Monnier
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=wc37jzw9a6u.fsf@mu.cis.ohio-state.edu \
--to=brutt+news@bloomington.in.us \
--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).