From: John Yates <john@yates-sheets.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: A vc wish: vc-timemachine
Date: Sun, 16 Oct 2022 07:49:19 -0400 [thread overview]
Message-ID: <CAJnXXognz4RDMHQKuXqWRfh4yvr59uFMh4M2ua7_5jr8UHZYLQ@mail.gmail.com> (raw)
In-Reply-To: <83a65w5o91.fsf@gnu.org>
On Sun, Oct 16, 2022 at 1:30 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> Doesn't vc-region-history (C-x v h) fit the bill?
No. vc-region-history's presents a concatenation of diffs.
git-timemachine is more akin to a non-existent
vc-revision-same-window. It is a minor mode applied to a buffer
visiting a version controlled file. It renders that buffer readonly
and then allows one to 'scroll' backward and forward over that file's
linear history, always showing a fully reconstructed revision, reusing
a single buffer.
My druthers would be for a vc-browse command that pops a new buffer
containing the most recently committed revision of the subject file.
It would support operations similar to git-timemachine:
* vc-browse-show-previous
* vc-browse-show-next
git-timemachine style refinements could include:
* vc-browse-show-commit
* vc-browse-show-annotation
* vc-browsw-goto-earlier-commit (regex search)
next prev parent reply other threads:[~2022-10-16 11:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 20:07 A vc wish: vc-timemachine John Yates
2022-10-15 20:25 ` Manuel Uberti
2022-10-16 5:30 ` Eli Zaretskii
2022-10-16 8:17 ` [vc-region-history in HG] (was: A vc wish: vc-timemachine) Uwe Brauer
2022-10-16 10:51 ` [vc-region-history in HG] Daniel Martín
2022-10-16 12:17 ` Uwe Brauer
2022-10-16 15:50 ` [It works] (was: [vc-region-history in HG]) Uwe Brauer
2022-10-16 13:58 ` [there is hg log -L] " Uwe Brauer
2022-10-16 11:49 ` John Yates [this message]
2022-10-16 22:29 ` A vc wish: vc-timemachine Dmitry Gutov
2022-10-17 1:26 ` John Yates
2022-10-17 19:12 ` Juri Linkov
2022-10-17 21:03 ` John Yates
2022-10-17 21:51 ` John Yates
2022-10-18 11:59 ` Richard Stallman
2022-10-18 14:46 ` John Yates
2022-10-21 19:42 ` Richard Stallman
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=CAJnXXognz4RDMHQKuXqWRfh4yvr59uFMh4M2ua7_5jr8UHZYLQ@mail.gmail.com \
--to=john@yates-sheets.org \
--cc=eliz@gnu.org \
--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).