bug#9087: Crash reading from minibuffer with icomplete-mode

[martin rudalics]

>> Thanks.  I'm beginning to understand.  Is post_character_message the
>> only potential source of this problem or are there others as well?
>
> There are others.  Search for the callers of signal_user_input, and
> you will find them.  E.g., it is called for mouse inputs as well.

I asked because I noticed these calls.  And indeed it crashes on mouse
input as well.

>> Naively asked: Could we avoid the problem if on normal input we did not
>> call signal_user_input but did something similar to C-g handling?
>
> We could, but why would we want to?  signal_user_input does TRT,
> except when immediate_quit is set.  If we don't call it, we won't be
> able to support throw-on-input and while-no-input.

I meant do the same as C-g when immediate_quit is set.

martin