From: Jeremy Morton <admin@game-point.net>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Strange bug with "git log" - pdftotext?
Date: Mon, 30 Jul 2018 16:51:33 +0100 [thread overview]
Message-ID: <5B5F3405.9070902@game-point.net> (raw)
In-Reply-To: <20180730153731.GA25797@sigill.intra.peff.net>
I discovered it was an issue with the version of Git for Windows I was
using. Upgraded to the latest version and it works now.
--
Best regards,
Jeremy Morton (Jez)
On 30/07/2018 16:37, Jeff King wrote:
> On Mon, Jul 30, 2018 at 01:49:46PM +0100, Jeremy Morton wrote:
>
>> I'm trying to search my git log history for a particular term -
>> "unobtrusive" - so I run this command:
>>
>> git log -S unobtrusive --oneline
>>
>> When I do this, this is displayed and I'm in an interactive less terminal or
>> something:
>>
>> pdftotext version 4.00
>> [...]
>
> That's definitely weird.
>
> My guess is that the repository has some .gitattributes set up to diff
> pdf files in a particular way, and you have some matching config that
> tries to call pdftotext.
>
> What does:
>
> git config --list | grep ^diff
>
> say? I'd expect to see an external or textconv option there running
> pdftotext.
>
> Another option is that your pager is somehow set up to call pdftotext,
> but that seems much more nonsensical to use the tool there (but try "git
> var GIT_PAGER" and "git config pager.log" to check).
>
> -Peff
>
next prev parent reply other threads:[~2018-07-30 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 12:49 Strange bug with "git log" - pdftotext? Jeremy Morton
2018-07-30 15:37 ` Jeff King
2018-07-30 15:51 ` Jeremy Morton [this message]
2018-07-30 15:41 ` stefan.naewe
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=5B5F3405.9070902@game-point.net \
--to=admin@game-point.net \
--cc=git@vger.kernel.org \
--cc=peff@peff.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.
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 NNTP newsgroup(s).