Thorsten Glaser wrote:
> Hi,
>
> do these have to be pipes? That got me wondering.
Yes, for most use cases I have run into they do need to be pipes and
not tempfiles. I do think =(...) is neat, too, but it is a distinct
feature.
Thanks,
Jonathan
--
To UNSUBSCRIBE, email to debian-bugs-dist-r
Hi,
do these have to be pipes? That got me wondering.
Otherwise, I could do a tree-level transform (except the IOREDIR
cases are again slightly more complex). Something like this:
• if <(command2) is contained in command1:
‣ allocate a tempfile
⇒ attach the tempfile to the list of cleanups
Thorsten Glaser wrote:
> Jonathan Nieder dixit[1]:
>> <( ... )- runs ... in a subshell in the background, with its
>>output connected to a pipe.
[...]
>> On Linux and similar OSes this is typically implemented using
>> /proc/fd. A more portable implementation would us
Jonathan Nieder dixit:
>This construct is also handy when one wants to update the current
>environment downstream from some other process.
process |&
while IFS= read -pr line; do
…
done
↑ is the proper ksh idiom for that.
> <( ... )- runs ... in
Package: mksh
Version: 39.3.20101101-1
Severity: wishlist
Tags: upstream
Hi Thorsten,
Recently I found myself debugging a pipeline with "tee".
Unfortunately the logs grew large very quickly, so as a stopgap
measure I used a compressor.
mkfifo backflow
... (xz -1 >log-one.xz) |
5 matches
Mail list logo
