[PATCH] Exit status by no-argument `return' for function calls in trap handlers

Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/

Re: [bug] PROMPT_COMMAND is not executed as expected in some situations

On 4/16/20 9:21 AM, Franklin, Jason wrote: > On 4/15/20 5:35 PM, Chet Ramey wrote: >> These all pretty much all fall into the category of the editor reprinting >> the prompt before it returns. > > Hmmm... > > So, is there no way to have Bash handle the printing of the prompt after > the return of

Re: [bug] PROMPT_COMMAND is not executed as expected in some situations

On 4/15/20 5:35 PM, Chet Ramey wrote: > These all pretty much all fall into the category of the editor reprinting > the prompt before it returns. Hmmm... So, is there no way to have Bash handle the printing of the prompt after the return of the command and of the editor? This would allow PROMPT_