From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: detect pipe
Date: Thu, 28 Jan 2021 07:45:10 -0800 [thread overview]
Message-ID: <14ce37b2-35ca-6002-474a-7de5d6626a66@eastlink.ca> (raw)
In-Reply-To: <560cef52-aee7-352a-2ba3-25826fe54136@eastlink.ca>
On 2021-01-28 7:05 a.m., Ray Andrews wrote:
Delays of some sort are part of this almost for sure. As it was, the
test for the pipe was a hundred lines down in my function. If I
simplify the alias and move the pipe test to the top of the function:
#alias g='tabs -4; noglob _g'
alias g='noglob _g'
function _g ()
{
local ppipe_flag=
[[ -p /dev/fd/0 ]] && ppipe_flag=1
... reliability increases to maybe 80%. Still, if I pipe directly into
' _g ', bypassing the alias, reliability is 100%. As for test1 and
test2 from last night, they are both 100% right now. Thursday's are
lucky. Funny thing, if ' g ' works ten times, then breaks, once
it's broke, it stays broke, I can run it ten more times and it won't fix
itself. Something changes in the OS I think.
next prev parent reply other threads:[~2021-01-28 15:45 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 [this message]
2021-01-28 20:58 ` Bart Schaefer
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=14ce37b2-35ca-6002-474a-7de5d6626a66@eastlink.ca \
--to=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).