[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-readline] [bug] Readline Ctrl-C in ipython pylab
From: |
Chet Ramey |
Subject: |
Re: [Bug-readline] [bug] Readline Ctrl-C in ipython pylab |
Date: |
Thu, 21 Apr 2016 10:17:34 -0700 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 |
On 4/21/16 9:54 AM, Carlos Pita wrote:
> Hi Chet,
>
> using readline-7.0-testing with ipython 4.1.2 and the TkAgg (or GTK3Agg)
> backend for matplotlib, I observed the following behavior:
>
> 1) open ipython in pylab mode (ipython --pylab or use the %pylab magic once
> inside the repl).
>
> 2) Type something.
>
> 3) Press Ctrl-C: line edition is not aborted as expected.
This is probably the result of the same signal handling issues as with
SIGWINCH that we discussed a little more than a year ago. Readline
catches the signal, sets a flag, and, when it's safe, resends it to the
calling application. It expects that if the calling application catches
SIGINT, it will take care of cleaning up the readline state. Sometimes
applications don't want to kill the current line on SIGINT.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU address@hidden http://cnswww.cns.cwru.edu/~chet/