Date:Sun, 19 Nov 2023 07:40:00 +1000
From:Martin D Kealey
Message-ID:
| The fact that you don't *want* the output of xclip connected to tr
| (because it makes tr wait for xclip *and all its children* to finish,
| while the shell waits for tr to finish) does no
On Nov 18 2023, Daniel Barrett via Bug reports for the GNU Bourne Again SHell
wrote:
> If it's helpful, here's another interesting piece of the puzzle: the
> "xsel -i" command (which also copies stdin to the X primary selection,
> like "xclip -i" does) works fine in the original pipeline, without
Perhaps some background would help here; I start by highlighting this
section in "man xclip":
-l, -loops
number of X selection requests (pastes into X applications)
to wait for before exiting, with a value of 0 (default) causing xclip to
wait for an unlimited number of reques
On November 18, 2023, Greg Wooledge wrote:
>On Sat, Nov 18, 2023 at 08:36:06AM -0500, dbarrett--- via Bug reports for the
>GNU Bourne Again SHell wrote:
>> echo foo | tee >(xclip -i) | tr o x
>>
>> The command does print "fxx" but then it hangs.
>>
>> The same command behaves correctly when run
On Nov 18 2023, Greg Wooledge wrote:
> On Sat, Nov 18, 2023 at 08:36:06AM -0500, dbarrett--- via Bug reports for the
> GNU Bourne Again SHell wrote:
>> echo foo | tee >(xclip -i) | tr o x
>>
>> The command does print "fxx" but then it hangs.
>>
>> The same command behaves correctly when run in
On Sat, Nov 18, 2023 at 08:36:06AM -0500, dbarrett--- via Bug reports for the
GNU Bourne Again SHell wrote:
> echo foo | tee >(xclip -i) | tr o x
>
> The command does print "fxx" but then it hangs.
>
> The same command behaves correctly when run in zsh.
For the record, here's what processes are
