bug-b...@trodman.com writes:
> foo | tee >(cat >&2) | bar
I do wonder how portable >( ... ) is in practice, versus the portability
of /dev/stderr. Maybe I worry about the former because I'm not
practiced in named-FIFO programming and so think of it as non-universal.
Dale
On Mon, Jul 06, 2020 at 03:03:15PM +0300, Ilkka Virta wrote:
> On 6.7. 14:37, Greg Wooledge wrote:
> > On Sat, Jul 04, 2020 at 01:42:00PM -0500, bug-b...@trodman.com wrote:
> > > but your soln is simplier. I assume /dev/stderr is on non linux UNIX
> > > also.
> >
> > It is *not*. It is not porta
On 6.7. 14:37, Greg Wooledge wrote:
On Sat, Jul 04, 2020 at 01:42:00PM -0500, bug-b...@trodman.com wrote:
but your soln is simplier. I assume /dev/stderr is on non linux UNIX
also.
It is *not*. It is not portable at all.
It works on macOS and I see mentions of it in man pages of the variou
On Fri, Jul 03, 2020 at 07:00:54PM +0100, Chris Elvidge wrote:
> I've used 'return $((!$#))' and 'return $[!$#]' to return an error if no
> parameters given to function.
The problem with this is that it *always* returns from the function,
even when paramters are given.
If you actually want to do
On Sat, Jul 04, 2020 at 01:42:00PM -0500, bug-b...@trodman.com wrote:
> On Fri 7/3/20 14:03 -0400 =?utf-8?Q?Lawrence_Vel=C3=A1zquez?= wrote:
> >What's wrong with `foo | tee /dev/stderr | bar`?
>
> but your soln is simplier. I assume /dev/stderr is on non linux UNIX
> also.
It is *not*. It is no
