From: Karl Chen <quarl@cs.berkeley.edu>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: emacs-devel@gnu.org
Subject: Re: vc-git-show-log-entry
Date: Mon, 20 Oct 2008 13:20:37 -0700 [thread overview]
Message-ID: <quack.20081020T1320.lth63nnnhm2@roar.cs.berkeley.edu> (raw)
In-Reply-To: <200810201819.m9KIJ6Wh024634@mothra.ics.uci.edu> (Dan Nicolaescu's message of "Mon\, 20 Oct 2008 11\:19\:06 -0700 \(PDT\)")
>>>>> On 2008-10-20 11:19 PDT, Dan Nicolaescu writes:
Dan> Karl Chen <quarl@cs.berkeley.edu> writes:
>> visiting a git-versioned file, when I do `vc-print-log',
>> point always moves to the end of the buffer instead of the
>> beginning.
Dan> It's hard to say what problem you are trying to report.
Dan> Can you please try again with a step by step description
Dan> of what you are doing, what are the results you are
Dan> getting and what are the expected results. Please start
Dan> from emacs -Q Please use emacs from CVS HEAD. It's
Dan> unlikely that another release will be made from the 22.x
Dan> branch.
git init
date > f1 ; git add *; git commit -m commit1
date >> f1 ; git add *; git commit -m commit2
emacs -Q f1
C-x C-v l
; point moves to the end of the *vc-change-log* buffer instead of
; the beginning.
As I said, if you undo the latest commit to vc-git.el, that fixes
it, but I suggest this replacement altogether.
(defun vc-git-show-log-entry (rev)
(log-view-goto-rev (vc-git-rev-parse rev)))
next prev parent reply other threads:[~2008-10-20 20:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 9:36 vc-git-show-log-entry Karl Chen
2008-10-20 15:01 ` vc-git-show-log-entry Eric Hanchrow
2008-10-20 15:09 ` vc-git-show-log-entry Eric Hanchrow
2008-10-20 18:19 ` vc-git-show-log-entry Dan Nicolaescu
2008-10-20 20:20 ` Karl Chen [this message]
2008-10-20 22:10 ` vc-git-show-log-entry Dan Nicolaescu
2008-10-21 7:23 ` vc-git-show-log-entry Karl Chen
2008-10-21 8:49 ` vc-git-show-log-entry Dan Nicolaescu
2008-10-21 17:52 ` vc-git-show-log-entry Alexandre Julliard
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=quack.20081020T1320.lth63nnnhm2@roar.cs.berkeley.edu \
--to=quarl@cs.berkeley.edu \
--cc=dann@ics.uci.edu \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.