all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 35624@debbugs.gnu.org
Subject: bug#35624: log-view-diff regression
Date: Thu, 16 May 2019 23:04:21 +0300	[thread overview]
Message-ID: <878sv6jhdm.fsf@mail.linkov.net> (raw)
In-Reply-To: <8c724814-923f-351a-686c-9f9c11468187@yandex.ru> (Dmitry Gutov's message of "Thu, 16 May 2019 01:05:11 +0300")

>>> You can also type 'C-u C-x v =', then '1.4', RET and C-j to omit the end
>>> version. That would also show the diff against the workfile.
>>
>> 10 keys more to type.
>
> You would normally paste the revision. And 'C-x v =' is already in my
> muscle memory.

Coping and then pasting requires more keypresses.

>> When this feature was enabled, I used it every day.
>
> Was it back in the days of CVS?

Nowadays I'm using it every day on Git: first I make the log buffer
writable by typing `C-x C-q', then type `C-o' at the top of the log
buffer to insert an empty line to make this feature available.

>> Currently I'm forced
>> to type 10 more keys every time.  I agree the log not to look weirder,
>> so better to not display Working.
>
> Could you explain what are you using it for? I understand a diff between
> revisions, and I understand a diff of the working tree against the index,
> but this kind of a diff seems pretty unusual.

The last time I used this feature today: I needed to revert some
previous commits partially, and before committing the reverting changes
I needed to check if necessary changes were reverted.  To do this, I
inserted an empty line at the top and set the beginning of the region here,
then set the end of the region on the line with the revision that
started a set of related commits.  Then just typed `=' and the displayed
diff confirmed that the right hunks were reverted, showing the diff
as it should have looked like without these reverted changes.

>> Or course, you didn't think about it, because you didn't know it exists.
>> I didn't know too until discovered it accidentally.  After that it hard
>> to lose this ability.  The problem is that this useful feature is
>> undocumented.  Here is the patch that documents it:
>
> I have tried to imagine using it, but it's still hard. Maybe doing it once
> a few days to compare the current progress against the master
> branch.

Yes, I believe a try is worth a thousand words.

> Though C-u C-x v d master RET C-j might be faster that looking for
> the revision that corresponds to the master branch in the log.

The log buffer helps to select the revisions to compare
because it displays dates and summaries of commits.





  reply	other threads:[~2019-05-16 20:04 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07 21:56 bug#35624: log-view-diff regression Juri Linkov
2019-05-07 22:54 ` Dmitry Gutov
2019-05-08 19:52   ` Juri Linkov
2019-05-09 13:26     ` Dmitry Gutov
2019-05-09 19:41       ` Juri Linkov
2019-05-10  0:14         ` Dmitry Gutov
2019-05-10  7:56           ` Eli Zaretskii
2019-05-11 20:58           ` Juri Linkov
2019-05-13  0:32             ` Dmitry Gutov
2019-05-13 20:40               ` Juri Linkov
2019-05-13 21:21                 ` Dmitry Gutov
2019-05-14 20:29                   ` Juri Linkov
2019-05-15  0:34                     ` Dmitry Gutov
2019-05-15 21:12                       ` Juri Linkov
2019-05-15 22:05                         ` Dmitry Gutov
2019-05-16 20:04                           ` Juri Linkov [this message]
2019-05-19 20:11                             ` Juri Linkov
2019-05-20 23:29                               ` Dmitry Gutov
2019-05-21 20:12                                 ` Juri Linkov
2019-05-21 20:39                                   ` Dmitry Gutov
2019-05-21 21:32                                     ` Juri Linkov
2019-05-21 21:52                                       ` Dmitry Gutov
2019-05-22 21:52                                         ` Dmitry Gutov
2019-05-23 21:07                                         ` Juri Linkov
2019-05-24  1:29                                           ` Dmitry Gutov
2019-05-24 18:41                                             ` Juri Linkov
2019-05-27 15:26                                               ` Dmitry Gutov
2019-05-27 19:47                                                 ` Juri Linkov
2019-06-10  0:57                                                   ` Dmitry Gutov
2019-06-10 20:50                                                     ` Juri Linkov
2019-06-10 22:19                                                       ` Dmitry Gutov
2019-06-16  0:55                                                   ` Dmitry Gutov
2019-06-16 20:13                                                     ` Juri Linkov
2019-06-17 13:48                                                       ` Dmitry Gutov
2019-06-17 20:42                                                         ` Juri Linkov
2019-06-17 22:23                                                           ` Dmitry Gutov
2019-05-20 23:39                             ` Dmitry Gutov
2019-05-10  7:54     ` Eli Zaretskii
2019-05-08  6:01 ` Eli Zaretskii
2019-05-08 19:52   ` Juri Linkov
2019-05-10  7:51     ` Eli Zaretskii
2019-05-11 20:53       ` Juri Linkov
2019-05-12  2:36         ` Eli Zaretskii
2019-05-12 19:15           ` Juri Linkov
2019-05-13 14:24             ` Eli Zaretskii
2019-05-13 14:44               ` Dmitry Gutov
2019-05-13 15:09                 ` Eli Zaretskii

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=878sv6jhdm.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=35624@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    /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.