From: John Yates <john@yates-sheets.org>
To: Juri Linkov <juri@linkov.net>
Cc: Dmitry Gutov <dgutov@yandex.ru>, Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: A vc wish: vc-timemachine
Date: Mon, 17 Oct 2022 17:51:16 -0400 [thread overview]
Message-ID: <CAJnXXojnb08UmVO9Sjcd9jhvN25ogZh0JC9sugbuGvUGcMpXqg@mail.gmail.com> (raw)
In-Reply-To: <CAJnXXoiK_qW+s_N-b0978UAmpePOtjT4+G1+vq7MAjUWiV50VA@mail.gmail.com>
On Mon, Oct 17, 2022 at 5:03 PM John Yates <john@yates-sheets.org> wrote:
>
> That said, that optimization can be significant when looking for a revision, if the subject code has been heavily edited.
To make that more concrete...
My backup scheme records an RCS revision everytime I save a file:
https://github.com/jsyjr/bostr (A save is non-interaction and hence
records no meaningful commit comment.)
When something goes wrong I want to browse the various previous saved
states, searching for one that "looks right". Here "looks right" is
based on what I remember the code looking like at some point in the
past. The image in my memory is emphatically not a diff, nor a blame
display. Typically it was some prog-mode buffer with font-locking.
Having to drive my search process from some alternate revision
enumeration and having to separately bring up a view of each revision
is just a painful amount of friction.
Re: scratching my own itch...
I am trying to prototype something based on Peter Stiernström's
git-timemachine. Initially it will only support git, so, initially,
not a solution for my itch. But it will help me get my feet wet with
vc and will provide a means for others to "kick the ui tires".
next prev parent reply other threads:[~2022-10-17 21:51 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 ` A vc wish: vc-timemachine John Yates
2022-10-16 22:29 ` 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 [this message]
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=CAJnXXojnb08UmVO9Sjcd9jhvN25ogZh0JC9sugbuGvUGcMpXqg@mail.gmail.com \
--to=john@yates-sheets.org \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
/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).