From: Jeremy Morton <admin@game-point.net>
To: git@vger.kernel.org
Subject: Strange bug with "git log" - pdftotext?
Date: Mon, 30 Jul 2018 13:49:46 +0100 [thread overview]
Message-ID: <5B5F096A.7030404@game-point.net> (raw)
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
Copyright 1996-2017 Glyph & Cog, LLC
Usage: pdftotext [options] <PDF-file> [<text-file>]
-f <int> : first page to convert
-l <int> : last page to convert
-layout : maintain original physical layout
-simple : simple one-column page layout
-table : similar to -layout, but optimized for tables
-lineprinter : use strict fixed-pitch/height layout
-raw : keep strings in content stream order
-fixed <number> : assume fixed-pitch (or tabular) text
-linespacing <number>: fixed line spacing for LinePrinter mode
-clip : separate clipped text
-nodiag : discard diagonal text
-enc <string> : output text encoding name
-eol <string> : output end-of-line convention (unix, dos, or mac)
-nopgbrk : don't insert page breaks between pages
-bom : insert a Unicode BOM at the start of the text
file
-opw <string> : owner password (for encrypted files)
-upw <string> : user password (for encrypted files)
-q : don't print any messages or errors
-cfg <string> : configuration file to use in place of .xpdfrc
-v : print copyright and version info
:
When I hit the down arrow, it scrolls down, repeating this output
infinitely until I hit 'q'. What is going on here??
--
Best regards,
Jeremy Morton (Jez)
next reply other threads:[~2018-07-30 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 12:49 Jeremy Morton [this message]
2018-07-30 15:37 ` Strange bug with "git log" - pdftotext? Jeff King
2018-07-30 15:51 ` Jeremy Morton
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=5B5F096A.7030404@game-point.net \
--to=admin@game-point.net \
--cc=git@vger.kernel.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.
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.