[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: |& in bash?
From: |
John Caruso |
Subject: |
Re: |& in bash? |
Date: |
Mon, 21 Jan 2013 18:20:35 +0000 (UTC) |
User-agent: |
slrn/0.9.7.4 (Win32) |
In article <mailman.17846.1358543463.855.bug-bash@gnu.org>, Dan Douglas wrote:
> It isn't very common to dump multiple streams into one pipe.
echo "n't very" >/dev/null 2>&1
> I suggest avoiding |&.
Personally I wouldn't use it in scripts, since I try to stick as close
to plain vanilla Bourne shell as possible (though that's not as much of
a consideration these days as it used to be). But for interactive use
it's one of the greatest shell time- and effort-savers I know of, and
I'm very happy to hear it's made its way into bash. I wouldn't suggest
avoiding it unless you like carpal tunnel.
- John
- |& in bash?, John Caruso, 2013/01/17
- Re: |& in bash?, Chet Ramey, 2013/01/17
- Message not available
- Message not available
- Re: |& in bash?,
John Caruso <=
- Re: |& in bash?, Steven W. Orr, 2013/01/22
- Re: |& in bash?, Greg Wooledge, 2013/01/22
- Re: |& in bash?, Bob Proulx, 2013/01/22
- Re: |& in bash?, Andreas Schwab, 2013/01/22
- Re: |& in bash?, DJ Mills, 2013/01/22
- Re: |& in bash?, Andreas Schwab, 2013/01/23
- Re: |& in bash?, Greg Wooledge, 2013/01/22
- Re: |& in bash?, Bob Proulx, 2013/01/22
- Re: |& in bash?, Linda Walsh, 2013/01/26