Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14787
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: exiting noninteractive shells on 'shift 2' |
| Date | 2018-11-09 11:42 -0500 |
| Message-ID | <mailman.3754.1541781763.1284.bug-bash@gnu.org> (permalink) |
| References | <cd413815-9523-f280-3ef3-fcd21bf7119e@redhat.com> <d8601773-69c8-16d1-82ab-5068d63bb24d@case.edu> <9ced783a-1c2b-f2c8-2287-fc0f6b967fa8@redhat.com> <fbe5c62d-d633-2fa5-32d1-591ff41a23cc@case.edu> <685c4d41-dcf1-61bc-0b65-04e2b180d568@redhat.com> |
On 11/9/18 11:22 AM, Eric Blake wrote: > On 11/9/18 8:52 AM, Chet Ramey wrote: >> On 11/9/18 9:47 AM, Eric Blake wrote: >> >>> Well, there's STILL a conformance issue - the standard requires that unless >>> documented otherwise, any time a command line tool exits with non-zero >>> status, that it outputs a message to stderr explaining the error. >> >> Where? >> > A diagnostic message shall be written to standard error whenever an > error condition occurs." > > Since 'shift 2' when $# is 1 is an error, and results in non-zero status, > it should print a diagnostic to stderr. So maybe the thing to do is to turn on the shift_verbose option in posix mode. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: exiting noninteractive shells on 'shift 2' Chet Ramey <chet.ramey@case.edu> - 2018-11-09 11:42 -0500
csiph-web