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

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

[Octave-bug-tracker] [bug #57902] Confusing debug output from commands e


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #57902] Confusing debug output from commands executed with "Run Selection"
Date: Wed, 26 Feb 2020 15:07:32 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

Follow-up Comment #5, bug #57902 (project octave):

When using the run selection feature of the GUI, in what context are the
selected lines supposed to run?  To be predictable, I'm assuming they should
be run in some kind of dummy context where no other variables are defined. 
That doesn't seem to be what is happening now.  If I create a variable in the
top-level workspace at the command line (say, x = 13) then in the editor run a
selection that contains "x", I'll get the value of the variable from the
top-level workspace.  Is that what Matlab users expect?

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57902>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

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