On 2/13/12 6:12 PM, Bruce Korb wrote:
> Hi Eric,
>
> On Mon, Feb 13, 2012 at 2:56 PM, Eric Blake wrote:
>> On 02/13/2012 03:50 PM, Bruce Korb wrote:
>>> It is very disconcerting and makes me want to press it an extra time.
>>> This is new behavior. Thanks.
>>
>> It works fine for me. Most likel
Hi Eric,
On Mon, Feb 13, 2012 at 2:56 PM, Eric Blake wrote:
> On 02/13/2012 03:50 PM, Bruce Korb wrote:
>> It is very disconcerting and makes me want to press it an extra time.
>> This is new behavior. Thanks.
>
> It works fine for me. Most likely, you have a bug in your ~/.inputrc
> file, whic
> -Original Message-
> From: Chet Ramey [mailto:chet.ra...@case.edu]
> Sent: Monday, February 13, 2012 5:05 AM
> To: Ewan Mellor
> Cc: Renuka Apte; bug-bash@gnu.org; chet.ra...@case.edu
> Subject: Re: set -e, bad substitutions, and trap EXIT
>
> On 2/13/12 4:43 AM, Ewan Mellor wrote:
>
>
On 02/13/2012 03:50 PM, Bruce Korb wrote:
> It is very disconcerting and makes me want to press it an extra time.
> This is new behavior. Thanks.
It works fine for me. Most likely, you have a bug in your ~/.inputrc
file, which is accidentally mapping 'T' to a readline-related function
rather tha
It is very disconcerting and makes me want to press it an extra time.
This is new behavior. Thanks.
On 2/13/12 4:43 AM, Ewan Mellor wrote:
>> Yes, it's a bug. When -e is in effect, the exit status is not set
>> before the shell exits. When it isn't, the code path taken results in
>> the correct exit status.
>>
>> Here's a patch that solves this particular problem.
>
> Thanks Chet. What happe
> -Original Message-
> From: Chet Ramey [mailto:chet.ra...@case.edu]
> Sent: 08 February 2012 10:45
> To: Ewan Mellor
> Cc: bug-bash@gnu.org; Renuka Apte; chet.ra...@case.edu
> Subject: Re: set -e, bad substitutions, and trap EXIT
>
> On 2/6/12 8:18 PM, Ewan Mellor wrote:
> > Hi,
> >
> > I
