From mint-bounce@lists.fishpool.fi Fri Jul 16 18:29:03 2010 Message-ID: <4C40DC85.8010204@freesbee.fr> Date: Sat, 17 Jul 2010 00:26:13 +0200 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.4) Gecko/20100608 Thunderbird/3.1 MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: [MiNT] readline 6.0 (in bash 4.1) References: <4C389D1D.7030108@freesbee.fr> <1278789068.7311.1378.camel@jetpack.demon.co.uk> <4C39FD60.7040409@freesbee.fr> <1279270998.26377.1077.camel@jetpack.demon.co.uk> In-Reply-To: <1279270998.26377.1077.camel@jetpack.demon.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: vincent.riviere@freesbee.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o6GMT3L4013991 Alan Hourihane wrote: > Remember that bash 3.2 didn't have this problem, so it'd be worth > investigating what changed. A new asynchronous signal handling has been introduced in readline 6.0. Especially, there is a new variable named _rl_interrupt_immediately which indicates if the signal must be handled immediately or asynchronously. I have tried the following change in lib/readline/signals.c: static RETSIGTYPE rl_signal_handler (sig) int sig; { if (1/*_rl_interrupt_immediately || RL_ISSTATE(RL_STATE_CALLBACK)*/) { The behaviour seems to be OK now, but I'm absolutely not sure it is correct. Some ideas for further investigation here: http://osdir.com/ml/bug-readline-gnu/2009-11/msg00001.html http://comments.gmane.org/gmane.comp.gnu.readline/43 http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg708760.html -- Vincent Rivière