From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-devel@gnu.org
Subject: Re: (vc-annotate-revision-previous-to-line) rcs, cannot go back
Date: Sat, 20 Apr 2013 11:42:06 +0200 [thread overview]
Message-ID: <87ip3hwnbl.fsf@zigzag.favinet> (raw)
In-Reply-To: <87haj2stkw.fsf@gilgamesch.quim.ucm.es> (Uwe Brauer's message of "Fri, 19 Apr 2013 12:28:15 +0200")
[-- Attachment #1.1: Type: text/plain, Size: 206 bytes --]
() Uwe Brauer <oub@mat.ucm.es>
() Fri, 19 Apr 2013 12:28:15 +0200
1.1 1.2 1.3 1.4
2.1 2.2
[...]
Anybody knows about a hack to achieve jumping from 2.1 to 1.4.
Here's a quick and dirty hack:
[-- Attachment #1.2: vc-rcs-previous-revision.el --]
[-- Type: application/emacs-lisp, Size: 1232 bytes --]
[-- Attachment #1.3: Type: text/plain, Size: 14 bytes --]
Tested with:
[-- Attachment #1.4: mkfoo --]
[-- Type: application/shell-script, Size: 280 bytes --]
[-- Attachment #1.5: Type: text/plain, Size: 422 bytes --]
and: C-x C-f /tmp/foo RET
M->
C-x v g
p
p
p
p
p
p
It's dirty because it calls rlog(1) directly, sidestepping the VC
abstractions, and what's worse, that info was already laboriously
computed in the process of preparing the annotation buffer, then
discarded (the infelicity is not limited to this function). :-/
--
Thien-Thi Nguyen
GPG key: 4C807502
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2013-04-20 9:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 10:28 (vc-annotate-revision-previous-to-line) rcs, cannot go back Uwe Brauer
2013-04-20 9:42 ` Thien-Thi Nguyen [this message]
2013-04-20 10:08 ` Uwe Brauer
2013-04-20 11:22 ` Thien-Thi Nguyen
2013-04-20 17:01 ` Uwe Brauer
2013-04-23 20:32 ` Uwe Brauer
2013-04-24 2:25 ` Thien-Thi Nguyen
2013-04-27 16:40 ` vc-annotate-show-diff- (was: (vc-annotate-revision-previous-to-line) rcs, cannot go back) Uwe Brauer
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=87ip3hwnbl.fsf@zigzag.favinet \
--to=ttn@gnuvola.org \
--cc=emacs-devel@gnu.org \
--cc=oub@mat.ucm.es \
/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).