From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: xargs with zsh function
Date: Tue, 19 Jan 2021 15:48:22 -0800 [thread overview]
Message-ID: <dc9af700-7e15-2e56-3818-3f2f1983f092@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7bFZpTWJkJ4RSkx2hg11Dxj-fQV1Wvt6EcN7bQKtxmJnA@mail.gmail.com>
On 2021-01-19 1:39 p.m., Bart Schaefer wrote:
> On Tue, Jan 19, 2021 at 12:27 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>> My strong preference would be that zargs be agnostic as to one's
>> environment and functions called by it would behave exactly as
>> otherwise.
> That's what the zargs_patch.txt in my other message is supposed to do.
>
>> I'd like to be able to link my functions together
>> via piping+zargs.
> Pipelines are for linking together things that expect to read standard
> input and write standard output.
>
> foo | bar
>
> is the same as
>
> foo > file
> bar < file
>
> except that the file is being simultaneously written and read
The above is much easier to understand and of course obviously simpler.
As I said,
the whole thing is a bit of a mystery. A lot of stuff attaches to ' | '
obviously.
> If you rejigger them into a pipeline, you
> force some of them into background subshells, and those are no longer
> able to affect the current shell. That may or may not be OK, but you
> should think about it.
Well again I have no idea what the intimacies of it are but at least the
notion of being able to
link functions analogously to what xargs does is desirable. If you have
a patch that does that for
zargs I'd sure like to have it.
next prev parent reply other threads:[~2021-01-19 23:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 23:12 Ray Andrews
2021-01-18 3:10 ` Bart Schaefer
2021-01-18 22:14 ` Ray Andrews
2021-01-18 23:09 ` Bart Schaefer
2021-01-19 5:18 ` Ray Andrews
2021-01-19 14:30 ` Ray Andrews
2021-01-19 17:52 ` Lawrence Velázquez
2021-01-19 20:27 ` Ray Andrews
2021-01-19 21:39 ` Bart Schaefer
2021-01-19 23:48 ` Ray Andrews [this message]
2021-01-20 1:05 ` Ray Andrews
2021-01-20 18:25 ` Ray Andrews
2021-01-21 5:52 ` Bart Schaefer
2021-01-21 19:55 ` Ray Andrews
2021-01-21 21:50 ` Bart Schaefer
2021-01-21 23:20 ` Ray Andrews
2021-01-19 20:31 ` Bart Schaefer
2021-01-19 20:59 ` Ray Andrews
2021-01-20 16:27 ` Daniel Shahaf
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=dc9af700-7e15-2e56-3818-3f2f1983f092@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).