[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: looking for consistent C-c trap behavior

From: gentoo_eshoes
Subject: Re: looking for consistent C-c trap behavior
Date: Sun, 19 Apr 2020 00:45:07 +0200 (CEST)

Apr 18, 2020, 23:41 by address@hidden:

> On another note, I naively tried to patch out the POSIX requirement, for my 
> own/local_use puposes but had no effect:
> in this code
> +  /* posix mode SIGINT during read -e. We only get here if SIGINT is 
> trapped. */
> +  if (posixly_correct && this_shell_builtin == read_builtin && sig == 2)
> +    {
> +      last_command_exit_value = 128|SIGINT;
> +      throw_to_top_level ();
> +    }
> by removing "posixly_correct &&" from above. I've no idea why that would have 
> no effect, a bit stumped.
> I've even tried with a prior 'make clean'. The only explanation is that some 
> other code that happens only during `POSIXly correct` mode is affecting this 
> somehow...
regarding the above, I stand corrected: it does indeed have effect but only on 
'read -e' (just as the comment states), that bash_event_hook() function isn't 
entered for 'read -p' which to me was surprising, yet no doubt correct(I'm 
The code that allows 'read -p' to be interrupted when posixly_correct, must 
then be somewhere else, I shall keep lookin', yet I fear I might not find it :-"

reply via email to

[Prev in Thread] Current Thread [Next in Thread]