zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: detect pipe
Date: Thu, 28 Jan 2021 12:58:07 -0800	[thread overview]
Message-ID: <CAH+w=7Yzj4CA6bjLcSm_4ciO0HWC4FqCw--tsJnP3fdDO40BvQ@mail.gmail.com> (raw)
In-Reply-To: <14ce37b2-35ca-6002-474a-7de5d6626a66@eastlink.ca>

On Thu, Jan 28, 2021 at 7:45 AM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> On 2021-01-28 7:05 a.m., Ray Andrews wrote:
>
> Delays of some sort are part of this almost for sure.
> Something changes in the OS I think.

Speaking of that, what OS are you using?

> #alias g='tabs -4; noglob _g'

That is guaranteed NOT to work.  With that alias in place, your pipe
is feeding into the "tabs" command, and then the _g function is run
with the regular shell standard input in place.  Aliases are
command-text-level replacements, so  given the above,

% echo something | g other

is the same as

% echo something | tabs -4; _g other

which (in case not already obvious) is just like

% echo something | tabs -4
% _g other

The only way that would ever report stdin as a pipe would be if it
appeared in a compound command context, something like one of

% echo something | { g other }
% echo something | ( g other }
% echo something | if g other; then ... fi
etc.


  reply	other threads:[~2021-01-28 20:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27 16:45 Ray Andrews
2021-01-27 23:59 ` Bart Schaefer
2021-01-28  4:57   ` Ray Andrews
2021-01-28  6:16     ` Bart Schaefer
2021-01-28 10:08     ` Vincent Lefevre
2021-01-28 10:28       ` Vincent Lefevre
2021-01-28 15:05         ` Ray Andrews
2021-01-28 15:45           ` Ray Andrews
2021-01-28 20:58             ` Bart Schaefer [this message]
2021-01-28 20:59               ` Bart Schaefer
2021-01-29  1:17               ` Ray Andrews
2021-01-29  2:50                 ` Bart Schaefer
2021-01-29  3:21                   ` Ray Andrews
2021-01-30  0:29                     ` Bart Schaefer
2021-01-30 14:26                       ` Ray Andrews
2021-01-30 19:00                         ` Bart Schaefer
2021-01-30 19:19                           ` Ray Andrews
2021-01-31 19:12                             ` Ray Andrews
2021-01-31 21:28                               ` Bart Schaefer
2021-02-14 17:31                           ` Vincent Lefevre
2021-02-14 19:33                             ` Bart Schaefer
2021-02-14 20:33                               ` Ray Andrews
2021-02-14 21:20                                 ` Bart Schaefer
2021-02-14 22:25                                   ` Ray Andrews
2021-02-14 21:24                                 ` Vincent Lefevre
2021-02-14 21:19                               ` Vincent Lefevre
2021-02-14 21:24                                 ` Bart Schaefer
2021-02-14 21:38                                 ` Bart Schaefer

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='CAH+w=7Yzj4CA6bjLcSm_4ciO0HWC4FqCw--tsJnP3fdDO40BvQ@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=rayandrews@eastlink.ca \
    --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).