octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #41322] Ctrl-C doesn't work correctly in inter


From: Stefan Mahr
Subject: [Octave-bug-tracker] [bug #41322] Ctrl-C doesn't work correctly in interactive mode while running with --no-gui option
Date: Thu, 23 Jan 2014 13:50:07 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/31.0.1650.63 Chrome/31.0.1650.63 Safari/537.36

URL:
  <http://savannah.gnu.org/bugs/?41322>

                 Summary: Ctrl-C doesn't work correctly in interactive mode
while running with --no-gui option
                 Project: GNU Octave
            Submitted by: dac922
            Submitted on: Do 23 Jan 2014 13:50:06 GMT
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Crash
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

If 'octave-cli' is used or 'octave' is used with GUI, it's no problem to use
Ctrl-C to abort the current input.

If octave is started with 'octave --no-gui', pressing Ctrl-C is not enough. An
additional ENTER is needed.

Sometimes, if Ctrl-C was pressed two or more times, octave segfaults once
ENTER is pressed.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?41322>

_______________________________________________
  Nachricht gesendet von/durch Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]