From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 20470@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
Raoul Gough <raoulgough@yahoo.co.uk>
Subject: bug#20470: 24.5; VC log buffer no longer scrolls itself
Date: Tue, 25 Aug 2020 21:30:08 +0300 [thread overview]
Message-ID: <87pn7ey4dj.fsf@mail.linkov.net> (raw)
In-Reply-To: <871rjvdqrb.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 25 Aug 2020 11:22:16 +0200")
> Apply the patch or close the bug as a "wontfix"?
>
> diff --git a/lisp/vc/vc.el b/lisp/vc/vc.el
> index 5561292d8c..6dad0cf83a 100644
> --- a/lisp/vc/vc.el
> +++ b/lisp/vc/vc.el
> @@ -817,6 +817,12 @@ vc-log-show-limit
> Not all VC backends are able to support this feature."
> :type 'integer)
>
> +(defcustom vc-log-jump-to-current nil
> + "If non-nil, `vc-print-log' moves point automatically to the
> +log message for the current working revision."
> + :type 'boolean
> + :version "28.1")
I think such option makes more sense in context of https://debbugs.gnu.org/35624#66
that proposed to insert a header line for the current working revision
where you can type 'D' to diff the working revision in vc-git logs.
But I'm still not sure whether such option is needed at all since
the long-established behavior is just to jump to the latest revision
that should be followed in all VCSs.
next prev parent reply other threads:[~2020-08-25 18:30 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 ` bug#20470: 24.5; VC log buffer no longer scrolls itself Stefan Monnier
2020-08-25 9:22 ` Lars Ingebrigtsen
2020-08-25 18:30 ` Juri Linkov [this message]
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=87pn7ey4dj.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=20470@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--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).