Thread View: gnu.bash.bug
2 messages
2 total messages
Started by James J Dempsey
Thu, 10 Aug 1989 19:24
suggestion: >>&
Author: James J Dempsey
Date: Thu, 10 Aug 1989 19:24
Date: Thu, 10 Aug 1989 19:24
7 lines
602 bytes
602 bytes
I like that you can do >& (or &>) in bash as a shorthand to send stdout and stderr to a file. It would be nice if >>& worked to append stdout and stderr to a file. I suppose to be consistent, you should also add &>>, but I wouldn't mind only one form of the >& >>& shorthands. --Jim--
Re: suggestion: >>&
Author: Arnold D. Robbins {EUCC}
Date: Fri, 11 Aug 1989 16:53
Date: Fri, 11 Aug 1989 16:53
16 lines
1265 bytes
1265 bytes
In article <8908101933.AA04226@life.ai.mit.edu> jjd@BBN.COM (James J Dempsey) writes: >I like that you can do >& (or &>) in bash as a shorthand to send >stdout and stderr to a file. It would be nice if >>& worked to append >stdout and stderr to a file. I suppose to be consistent, you should >also add &>>, but I wouldn't mind only one form of the >& >>& shorthands. Since BASH is supposed to be Bourne shell compatible program >> file 2>&1 will do the trick. No real need to add yet another syntax. -- Arnold Robbins -- Emory University Computing Center | Laundry increases DOMAIN: arnold@unix.cc.emory.edu | exponentially in the UUCP: gatech!emoryu1!arnold PHONE: +1 404 727-7636 | number of children. BITNET: arnold@emoryu1 FAX: +1 404 727-2599 | -- Miriam Hartholz
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads