GNU bug report logs - #9087
Crash reading from minibuffer with icomplete-mode

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: martin rudalics <rudalics <at> gmx.at>
Cc: claudio.bley <at> gmail.com, lekktu <at> gmail.com, 9087 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca, jasonr <at> gnu.org
Subject: bug#9087: Crash reading from minibuffer with icomplete-mode
Date: Sat, 07 Jan 2012 19:52:36 +0200

> Date: Sat, 07 Jan 2012 18:45:28 +0100
> From: martin rudalics <rudalics <at> gmx.at>
> CC: monnier <at> iro.umontreal.ca, jasonr <at> gnu.org, claudio.bley <at> gmail.com, 
>  lekktu <at> gmail.com, 9087 <at> debbugs.gnu.org
> 
>  > Details, please.  What exactly are you suggesting that we do instead
>  > of calling signal_user_input?
> 
> When immediate_quit is set proceed in signal_user_input as if we
> processed C-g in post_character_message.

That means we will call signal_quit that interrupts system calls (not
relevant to this case) and "forcibly complete any deferred messages"
(whatever that means) by calling cancel_all_deferred_msgs, which again
is not relevant.  By contrast, Vquit_flag will _not_ be set to
Vthrow_on_input, which will break throw-on-input and while-no-input.

IOW, all we do when we see C-g is interrupt any system calls and
deliver the C-g character to the main thread.  We do nothing special
besides that, AFAICS.  I don't see how this could help the case in
point.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.