[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #57161] [GUI] "Step in" button does not load f
From: |
Philip Nienhuis |
Subject: |
[Octave-bug-tracker] [bug #57161] [GUI] "Step in" button does not load function in editor |
Date: |
Sun, 3 Nov 2019 17:32:15 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 |
Update of bug #57161 (project octave):
Status: Confirmed => Invalid
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #3:
Yes Torsten that does it. Thanks!
The text you mention is:
"Always show debug breakpoints and pointers (open related file if closed)"
I figured files not in the editor would always be opened when "step in" is
clicked - what else would one expect "step in" to do in a GUI editor?
So I interpreted "...open related file if closed" more as a sort of warning
than as a selectable action, all the more because this text is between
parentheses.
My reasoning was that "step in" w/o seeing a file is just blind guessing.
Obviously "step in" is only useful if the file is open in another editor or on
hard copy, i.e., when using a CLI. Having a debugged file open in the GUI
editor and not opening stepped-in files in that same GUI editor seems
far-fetched.
But admittedly I can imagine that there can be user scenarios for it.
OK, closing as "invalid"
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?57161>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/