Re: [PATCH 1/1] Exit status of fc -e is the wrong way around

[Chet Ramey]

On 6/30/16 7:02 AM, Ingo Karkat wrote:

> Bash Version: 4.3
> Patch Level: 46
> Release Status: release
> Also seen in prior versions, at least down to 4.2.46(1)-release
> 
> Description:
> 
> I'm trying to edit and recall a previous command with Bash's built-in "fc -e 
> vi" command, but somehow the exit status always indicates failure (1) on 
> successful edit, even if that editing is a no-op. The recalled command itself 
> executes just fine, just $? is wrong.
> Originally reported (and more background) here: 
> http://unix.stackexchange.com/questions/292847/exit-status-of-fc-e-is-the-wrong-way-around

Thanks for the report.  This was fixed back in November, 2015:

http://lists.gnu.org/archive/html/bug-bash/2015-11/msg00107.html

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/

signature.asc
Description: OpenPGP digital signature