From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: [patch] add interactive browse of revisions from vc *Annotate* buffers
Date: 12 Jan 2004 12:06:28 +0100 [thread overview]
Message-ID: <m3llod8lzf.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <wc3n08tanby.fsf@mu.cis.ohio-state.edu>
Benjamin Rutt <brutt+news@bloomington.in.us> writes:
> I wrote this patch because I wanted to be able to browse forward and
> backwards to prev and next revisions from vc.el *Annotate* buffers.
> That way, I can see which member of my work group is responsible for
> entering a particular line of a CVS-controlled file (it's sometimes
> not enough to just vc-annotate a buffer, since sometimes users
> reformat or reindent lines of source code that they didn't originally
> write). This patch allows you, from a vc-annotate-mode buffer, to
> press C-c C-p to go to the previous revision and C-c C-n to go to the
> next revision. It's currently only implemented for CVS, since
> vc-annotate is only implemented for CVS anyway.
That is a very good feature indeed. Thanks!
However, I would like an extension to this feature so that
C-u C-c C-p
would pick up the revision from the current line of the annotate
buffer and annotate the previous revision to that revision, rather
than the revision of the work file as such.
This would make it easier to backtrack a specific change in case there
are many (unrelated) revision in the file.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2004-01-12 11:06 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 [this message]
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
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=m3llod8lzf.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--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).