Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #14789 > unrolled thread

Re: exiting noninteractive shells on 'shift 2'

Started byChet Ramey <chet.ramey@case.edu>
First post2018-11-09 11:55 -0500
Last post2018-11-09 11:55 -0500
Articles 1 — 1 participant

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: exiting noninteractive shells on 'shift 2' Chet Ramey <chet.ramey@case.edu> - 2018-11-09 11:55 -0500

#14789 — Re: exiting noninteractive shells on 'shift 2'

FromChet Ramey <chet.ramey@case.edu>
Date2018-11-09 11:55 -0500
SubjectRe: exiting noninteractive shells on 'shift 2'
Message-ID<mailman.3756.1541782550.1284.bug-bash@gnu.org>
On 11/9/18 11:46 AM, Eric Blake wrote:
> On 11/9/18 10:42 AM, Chet Ramey wrote:
> 
>>
>>>      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.
> 
> Cool - I didn't realize we already had a shopt for that. Yes, it sounds
> like in POSIX mode, shift_verbose should be turned on.
> 
> On a related note, should turning on POSIX mode also auto-enable xpg_echo?

No. That's just more of a can of worms than I want to deal with. Bash
claims strict conformance with both posix and xpg_echo enabled (that's what
the `strict-posix' configure option does, among other things).

-- 
``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/

[toc] | [standalone]


Back to top | Article view | gnu.bash.bug


csiph-web