From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-devel@gnu.org
Subject: Re: [vc-region-history in HG]
Date: Sun, 16 Oct 2022 14:17:39 +0200 [thread overview]
Message-ID: <87zgdwm07w.fsf@mat.ucm.es> (raw)
In-Reply-To: m1k050ghxt.fsf@yahoo.es
[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]
>>> "DM" == Daniel Martín <mardani29@yahoo.es> writes:
> Uwe Brauer <oub@mat.ucm.es> writes:
>>
>> I just realized that vc-region-history does not work in hg, in the sense
>> that it just shows the changes in the whole buffer, while it works for
>> git. I looked briefly at the code and could not find any special calls
>> to git there.
>>
>> Any idea what could be the reason (not that there are very many HG users
>> on this list...)?
> In a git repository, the function delegates to the backend function
> vc-git-region-history, which calls "git log -L" (requires git 1.8.4+).
> If this cheatsheet is accurate,
> https://hyperpolyglot.org/version-control, there is no direct Mercurial
> alternative to git log -L ("commits which touched lines").
Thanks!
Hm, I see, what is the difference then to annotate?
BTW I just found in vc-hg-region-history-mode
(define-derived-mode vc-hg-region-history-mode
vc-hg-log-view-mode "Hg-Region-History"
"Major mode to browse Hg's \"log -p\" output."
But this seems to be a different beast
> But perhaps we can implement the feature for Mercurial in some other
> way.
I try to contact some mercurial guru.
--
I strongly condemn Putin's war of aggression against the Ukraine.
I support to deliver weapons to Ukraine's military.
I support the ban of Russia from SWIFT.
I support the EU membership of the Ukraine.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2022-10-16 12:17 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 [this message]
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
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=87zgdwm07w.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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).