igorschein on Thu, 24 Sep 2009 17:29:50 +0200
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
- To: PARI developers <firstname.lastname@example.org>
- Subject: Re: break> prompt
- From: igorschein <email@example.com>
- Date: Thu, 24 Sep 2009 11:28:06 -0400
- Delivery-date: Thu, 24 Sep 2009 17:29:50 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=T4JUb+FROhxMdy3ntZf2lQ6z9ndrvBEfSm33rK/cyTQ=; b=aVKILblGCU2Xp52GTYOIJ6SPRfrOADY6iXG05q2oV9W+Adj8NqINRtGRK+M/AUMUwH 48tWOEpgk6DSzcP5QTlDC7NO8F8tUdCDFrdpFSJEqpnTAjSdu/7Iynx88a21u2bqD10/ QxBlG5MRSd8l0BbsM6PWB9cur6F7ulqAe0vvE=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=sILprI7YSVHAqQEGRklqqwQf4guxwtA1V2P2ptofEoBK/YZcSjriMwDIrIKRiTNm5f MOCz/ZPOUXX1scZAvloaxYtgv/y6+EjDcBqASjBKT5/ktHCjnCtgyu72Vg0YTqhlSMJY yUqLLUHSIeXZkUYEAQsKFo8InARWKs+V2H9no=
- In-reply-to: <20090924144601.GA21268@yellowpig>
- Mailing-list: contact firstname.lastname@example.org; run by ezmlm
- References: <email@example.com> <20090924144601.GA21268@yellowpig>
n Thu, Sep 24, 2009 at 10:46 AM, Bill Allombert <Bill.Allombert@math.u-bordeaux1.fr>
On Thu, Sep 24, 2009 at 09:47:55AM -0400, Igor Schein wrote:This is mostly intentional, see bug #958. The purpose of this change is
> In svn version 11882 ^C would take you from break> prompt to regular prompt,
> but in version 11961 it doesn't any more. Is it intentional or accidental?
to avoid the loss of a computation that you interrupted to look at its
progress. For example if you stop the computation to change the debug level
and make an error, you should still be allowed to continue the computation.
This include spurious ^C stroke.
Honestly, I did not know that ^C would get you out of the breakloop, and it is
> >From the point of convenience, I much prefer version 11882 behavior.
not documented. I suggest to use ^D instead.
Right, except that ^D is tricky - click it twice in a row by accident and you lose your 3 week-old session with 6000 lines of input and output. It'd be nice to be able to unbind ^D at the regular prompt, but because it's not a readline binding, it's not immediately obvious to me whether it's doable or not without mocking with shell and terminal settings. I'll switch to the 3rd option then - 3 ^Js in a row, which is much safer.