From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Raoul Gough <raoulgough@yahoo.co.uk>
Cc: 20470@debbugs.gnu.org
Subject: bug#20470: 24.5; VC log buffer no longer scrolls itself
Date: Fri, 01 May 2015 13:53:15 -0400 [thread overview]
Message-ID: <jwvd22k2nn1.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <1430400129.57087.YahooMailBasic@web171304.mail.ir2.yahoo.com> (Raoul Gough's message of "Thu, 30 Apr 2015 14:22:09 +0100")
> How to reproduce: open a file checked out from RCS, hit C-x v l (or
> equivalently M-x vc-print-log RET) and notice that the cursor ends up at
> the start of the *vc-change-log* buffer. It should jump to the log
> message for the current revision, which was the case until the fix for
> bug #15322 "VC log buffer scrolls itself"
How far are the two positions? What's between them?
> The particular revision control system doesn't really matter,
I'm beginning to suspect it does. IIRC RCS (and CVS) put a bunch of
file-level metadata before the actual log, whereas other VCSes just put
the log right away. So for RCS/CVS it might make sense to skip to the
first actual log message, so as to reproduce the behavior of
other backends.
Skipping to the log message corresponding to "the current revision"
seems much less important (and this is the part that was problematic
with the old behavior).
Stefan
next prev parent reply other threads:[~2015-05-01 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 13:22 bug#20470: 24.5; VC log buffer no longer scrolls itself Raoul Gough
2015-04-30 16:01 ` bug#20470: Acknowledgement (24.5; VC log buffer no longer scrolls itself) Raoul Gough
2015-05-01 17:53 ` Stefan Monnier [this message]
2020-08-25 9:22 ` bug#20470: 24.5; VC log buffer no longer scrolls itself Lars Ingebrigtsen
2020-08-25 18:30 ` Juri Linkov
2020-10-11 3:18 ` Lars Ingebrigtsen
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=jwvd22k2nn1.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=20470@debbugs.gnu.org \
--cc=raoulgough@yahoo.co.uk \
/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).