zsh-users
 help / color / mirror / code / Atom feed
From: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
To: zsh-users@zsh.org
Subject: Re: view onto command pipeline?
Date: Wed, 20 Jul 2022 15:27:36 -0400	[thread overview]
Message-ID: <YthXKBhzqU4m8tzS@fullerene.field.pennock-tech.net> (raw)
In-Reply-To: <a1cdc31b-b796-4721-8afa-1e8199c52fce@www.fastmail.com>

On 2022-07-20 at 07:23 -0400, Anthony Heading wrote:
> On Sat, Jul 16, 2022, at 5:30 PM, Bart Schaefer wrote:
> > You need to look at the preexec hook.
> 
> Ah, many thanks Bart!  Much appreciated.  Don't know how I missed that.
> 
> For the record, I used just the following, and it works great. 
> 
> git () {
>         local opts=() 
>         if [[ -o interactive && ( -t 1 || -n $pager ) ]]
>         then
>                 opts=(-c color.ui=always) 
>         fi
>         command git $opts $@
> }

So, "if invoked from shell, use color if stdout is a tty, otherwise
don't".  Since ancient Git (1.8.4) automatic-based-on-tty is the
default, so you'll need `git config --global color.ui false` run to
populate your gitconfig file to disable color normally.

The shell wrapping is simply:

    function git { command git -c color.ui=auto "$@" }

and only define this for interactive shells, so in .zshrc or the like,
not .zshenv.

-Phil


  parent reply	other threads:[~2022-07-20 19:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-16 16:15 Anthony Heading
2022-07-16 21:30 ` Bart Schaefer
2022-07-20 11:23   ` Anthony Heading
2022-07-20 11:37     ` Dominik Vogt
2022-07-20 12:22       ` Vincent Bernat
2022-07-20 12:35         ` Dominik Vogt
2022-07-20 19:07           ` Lawrence Velázquez
2022-07-21  0:15       ` Anthony Heading
2022-07-21  1:35         ` Lawrence Velázquez
2022-07-21  2:11           ` Anthony Heading
2022-07-21  3:15             ` Lawrence Velázquez
2022-07-21  6:43             ` Dominik Vogt
2022-08-04 21:12             ` Felipe Contreras
2022-07-20 19:27     ` Phil Pennock [this message]
2022-07-21  0:18       ` Anthony Heading

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=YthXKBhzqU4m8tzS@fullerene.field.pennock-tech.net \
    --to=zsh-workers+phil.pennock@spodhuis.org \
    --cc=zsh-users@zsh.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.vuxu.org/mirror/zsh/

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).