From: Mitchel Humpherys <mitch.special@gmail.com>
To: Davis Herring <herring@lanl.gov>
Cc: emacs-devel@gnu.org
Subject: Re: PATCH: vc-git-grep: force git-grep to disable color and pager
Date: Mon, 30 Sep 2013 20:51:19 -0700 [thread overview]
Message-ID: <CAOFALwJBBwmwh1h7hvj7eALuAgfR8GV-DqFV_=8uD1UO3AN-uA@mail.gmail.com> (raw)
In-Reply-To: <CAOFALwKgVcrT-RYQ2Xtyx20CXoeF0gj2i7546y-EyxvR0Xho3g@mail.gmail.com>
On Wed, Sep 25, 2013 at 10:17 PM, Mitchel Humpherys
<mitch.special@gmail.com> wrote:
> On Wed, Sep 25, 2013 at 10:08 AM, Davis Herring <herring@lanl.gov> wrote:
>>> This commit adds some command line options to the invocation of `git'
>>> in `vc-git-grep' so that git disables all coloring and paging. Without
>>> this, I get a warning about my "terminal" not being fully functional
>>> and git-grep attempts to use a pager (which means the git-grep process
>>> never finishes):
>>>
>>> git grep -n -e stuff -- *
>>> WARNING: terminal is not fully functional
>>> CREDITS:14:D: Alpha systems hacking, IPv6 and other network related stuff
>>> <snip>
>>> : <-- pager waiting for me to do something
>>
>> All this (including the warning) is the use of less, not the coloring
>> (although git might in theory complain if you try to use coloring with
>> no TERM variable or so). I'd recommend using --no-pager but trying to
>> interpret the color rather than suppressing it.
>>
>> Davis
>>
>
> You're absolutely right. I've removed the --no-color flag in this
> version and confirmed that highlighting works in the *grep* results
> buffer.
Any other comments on this? What's the next step towards merging? It's
quite a trivial patch but without it `vc-git-grep' is pretty much
unusable...
--
"if i had more time i would have written a shorter letter."
--Pascal
next prev parent reply other threads:[~2013-10-01 3:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 6:30 PATCH: vc-git-grep: force git-grep to disable color and pager Mitchel Humpherys
2013-09-25 17:08 ` Davis Herring
2013-09-26 5:17 ` Mitchel Humpherys
2013-10-01 3:51 ` Mitchel Humpherys [this message]
2013-10-01 15:34 ` Stefan Monnier
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='CAOFALwJBBwmwh1h7hvj7eALuAgfR8GV-DqFV_=8uD1UO3AN-uA@mail.gmail.com' \
--to=mitch.special@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=herring@lanl.gov \
/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.