From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: vc-region-history: HG?
Date: Tue, 16 Jan 2018 22:04:32 +0100 [thread overview]
Message-ID: <87shb5tt0f.fsf@telefonica.net> (raw)
In-Reply-To: CAPM58ojzBxoV7L8NcV5n07_mPpE34sAFJ_=tMdC3P4z-qfK+bQ@mail.gmail.com
Richard Copley <rcopley@gmail.com> writes:
> On 16 January 2018 at 18:41, Óscar Fuentes <ofv@wanadoo.es> wrote:
>> Uwe Brauer <oub@mat.ucm.es> writes:
>>
>>> But, what is the underlying git command? I tried to debug the function
>>> and couldn't figure it out.
>
> Uwe,
>
> To see the backend command, set 'vc-command-messages' to t
> before issuing a VC command in Emacs.
>
> For vc-command history the messages logged are:
>
> Running git --no-pager diff-index --exit-code -p HEAD -- Makefile.in
> in foreground...
> Running git --no-pager diff-index --exit-code -p HEAD -- Makefile.in...OK = 0
> Running git --no-pager log -p -L... . in background... done
>
> In this case I'm not sure that tells the whole story and I expect Emacs does
> some of the work. I didn't put much effort into understanding the output but
> perhaps it will give you a useful hint.
>
>> From vc-git-region-history:
>>
>> (vc-git-command buffer 'async nil "log" "-p" ;"--follow" ;FIXME: not supported?
>> (format "-L%d,%d:%s" lfrom lto (file-relative-name file)))
>>
>>
>> lfrom and lto are line numbers.
In case it is not clear, the command is
git log -p -L10,20:foo.c
for printing the history of lines 10 to 20 of file foo.c
next prev parent reply other threads:[~2018-01-16 21:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 14:27 vc-region-history: HG? Uwe Brauer
2018-01-16 17:15 ` Eli Zaretskii
2018-01-16 18:08 ` Uwe Brauer
2018-01-16 18:41 ` Óscar Fuentes
2018-01-16 19:08 ` Richard Copley
2018-01-16 19:09 ` Richard Copley
2018-01-16 21:04 ` Óscar Fuentes [this message]
2018-01-16 21:09 ` Richard Copley
2018-01-16 21:15 ` Stefan Monnier
2018-01-16 21:26 ` Uwe Brauer
2018-01-17 16:54 ` Uwe Brauer
2018-01-16 21:25 ` Uwe Brauer
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=87shb5tt0f.fsf@telefonica.net \
--to=ofv@wanadoo.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 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.