[Top][All Lists]

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

[Octave-bug-tracker] [bug #56738] Running a multi-line selection in the

From: Torsten Lilge
Subject: [Octave-bug-tracker] [bug #56738] Running a multi-line selection in the editor does not work anymore
Date: Fri, 9 Aug 2019 15:36:03 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/11.0 Safari/605.1.15 Epiphany/605.1.15


                 Summary: Running a multi-line selection in the editor does
not work anymore
                 Project: GNU Octave
            Submitted by: ttl
            Submitted on: Fri 09 Aug 2019 09:36:01 PM CEST
                Category: GUI
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Regression
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux



When running a multi-line selection in the editor, only the last line is
really executed. Example: 

Runing the selection

a = 1
b = 2
c = 3

from the editor leads to the result in the console window

>> a = 1

c =  3
>> b = 2

Only c = 3 is executed, a and b are still undefined afterwards. The previous
commands for a and b were only written into the command line and probably were
replaced by the following command before execution. Therefore, b = 2 is
restored after c = 3 has been executed. 

jwe, could this be a regression from changeset 420611c61298 (eliminating the
cmd-classes)? I remember that I have implemented the extra queue of cmd
objects in the gui because of similar issues, i.e., dropping command requests
from the gui in case of several commands in a sequence.


Reply to this item at:


  Message sent via Savannah

reply via email to

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