bugGNU Octave - Bugs: bug #57191, Ctrl-C does not work in GUI

 
 

bug #57191: Ctrl-C does not work in GUI

Submitter:  Lars Kindermann <larskindermann>
Submitted:  Fri 08 Nov 2019 10:28:47 AM UTC
   
 
Category:  GUI Severity:  2 - Minor
Priority:  3 - Low Item Group:  Regression
Status:  Fixed Assigned to:  None
Originator Name:  Open/Closed:  * Closed
Release:  * dev Operating System:  * GNU/Linux
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Fri 08 Nov 2019 01:41:21 PM UTC, comment #5: 

Closing report as fixed.

Pantxo Diribarne <pantxo>
Group Member
Fri 08 Nov 2019 01:35:22 PM UTC, comment #4: 

ok, fixed by jwe's last commit:
"make Ctrl-C work as interrupt in command window again"
I built just before that commit...

To clarify the "as expected":

When I start any X11 program from the commandline in a terminal, I naively expect that typing CTRL-C in that terminal will kill it. I just tried many GUIs on my system and did not find any other that won't behave like that.

Eg. maxima commandline catches Ctrl-C but xmaxima is killed...


Lars Kindermann <larskindermann>
Fri 08 Nov 2019 12:43:55 PM UTC, comment #3: 

Whoops I did not read carefully enough the statement

> a Ctrl-C in that terminal does not kill Octave as expected


My understanding was the bug fixed by jwe.

> Ctrl-C does not interrupt loops in the GUI.


For Octave dev and 5.1.0 I can kill the OP mentioned loop in the GUI terminal widget and the octave-cli versions.

Agree to comment #2. This use case I do not understand and would surprise me as well.  If Octave hangs, you must usually kill the process.

Kai Torben Ohlhus <siko1056>
Group Member
Fri 08 Nov 2019 12:27:01 PM UTC, comment #2: 

I observe the same as the OP in both Octave 5.1 and Octave 6.0 (id 959a63d1ede6). Pressing Ctrl+C in the launching terminal interrupts the loop in the GUI terminal, as it would do if I pressed Ctrl+C in the GUI terminal,  and does not kill Octave. But:

  • Don't know if it ever worked differently.
  • Don't have an opinion on whether Ctrl+C in the launching terminal should kill Octave


@Lars: I don't understand when you say "No problem with the commandline version". When using the command line, we expect Ctrl+C to interrupt the loop, not to kill Octave otherwise you wouldn't have a means to interrupt a loop without killing the process.

Pantxo Diribarne <pantxo>
Group Member
Fri 08 Nov 2019 11:12:38 AM UTC, comment #1: 

When talking about the dev branch, please always report the output for


>> __octave_config_info__ ("hg_id")
ans = 959a63d1ede6


jwe recently pushed a cset for this issue: https://hg.savannah.gnu.org/hgweb/octave/rev/959a63d1ede6

Is this fixed by updating your build tree to that version?

Kai Torben Ohlhus <siko1056>
Group Member
Fri 08 Nov 2019 10:28:47 AM UTC, original submission:  

Ctrl-C does not interrupt loops in the GUI.


a=1;while 1;a=a+1,end


No problem with the commandline version.

If the GUI is started from a terminal, a Ctrl-C in that terminal does not kill Octave as expected, but interrupts the loop instead.

Lars Kindermann <larskindermann>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by pantxo (Posted a comment)
  • -email is unavailable- added by siko1056 (Posted a comment)
  • -email is unavailable- added by larskindermann (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2019-11-08 pantxo StatusWorks For Me Fixed
        Open/ClosedOpen Closed
    2019-11-08 siko1056 Severity3 - Normal 2 - Minor
        Priority5 - Normal 3 - Low
        StatusNone Works For Me

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code