Issue 627 in direnv's github project show:
To reproduce this simply:
PROMPT_COMMAND="trap -- '' SIGINT; sleep 0.1; trap SIGINT;"
read foo
^C -- will exit current shell --
On Mon, Oct 12, 2020 at 09:52:21PM -0700, Daniel Farina wrote:
> On Sun, Oct 11, 2020 at 12:59 PM Che
On 10/13/20 3:38 AM, felix wrote:
> Issue 627 in direnv's github project show:
>
> To reproduce this simply:
>
> PROMPT_COMMAND="trap -- '' SIGINT; sleep 0.1; trap SIGINT;"
> read foo
> ^C -- will exit current shell --
Thanks, this is easy to work with.
The fix is to note
Hi Chet, hi all!
> In general, variable expansion errors cause posix-mode shells to exit and
> bash default mode shells to abort execution of the current command and
> return to the top level, whether that is the command line or the next
> command in the script. This aborts lists and other compoun
> On Oct 13, 2020, at 4:42 PM, Martin Schulte wrote:
>
> Hi Chet, hi all!
>
>> In general, variable expansion errors cause posix-mode shells to exit and
>> bash default mode shells to abort execution of the current command and
>> return to the top level, whether that is the command line or the n
Hello Lawrence, hello *!
> >> However, invalid parameter transformation operators are not considered
> >> fatal errors, even in posix mode. Maybe they should be.
> >
> > Yes, please :-)
> >
> > Or no error at all.
>
> Why should invalid parameter transformation operators be treated
> differentl
