zsh-users
 help / color / mirror / code / Atom feed
From: "Anthony Heading" <ajrh@ajrh.net>
To: zsh-users@zsh.org
Subject: Re: view onto command pipeline?
Date: Wed, 20 Jul 2022 20:18:19 -0400	[thread overview]
Message-ID: <fa9ddbdd-3bbb-419d-b760-74405c79457b@www.fastmail.com> (raw)
In-Reply-To: <YthXKBhzqU4m8tzS@fullerene.field.pennock-tech.net>

On Wed, Jul 20, 2022, at 3:27 PM, Phil Pennock wrote:
>     function git { command git -c color.ui=auto "$@" }

Maybe you missed the clever bit that Bart helped with?  As far as I know, these
'auto' settings can only detect a tty, they can't detect a pipe that happens to feed a tty.
Hence the panoply of command-line options and environment variables that Unix color needs.

I had been wondering about OS support to create a more standard mechanism, but it seems
impossible?   A fcntl(F_TTY) flag bit that can be set on a pipe to hint that it should be
treated like a tty would seem like a start, but maybe nothing short of an end-to-end handshake negotiation along the pipeline is going to work, and then maybe that's not Unix any more.

Obviously yes git has an automatic pager option,  probably as another workaround for this, but personally I just want to type '| less',  invariant to whether I'm running git diff or plain diff.   For the same reason agree the -t 1 test might be redundant for the default git config, but not
for all other commands or scenarios.


      reply	other threads:[~2022-07-21  0:24 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
2022-07-21  0:18       ` Anthony Heading [this message]

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=fa9ddbdd-3bbb-419d-b760-74405c79457b@www.fastmail.com \
    --to=ajrh@ajrh.net \
    --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).