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

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

[Octave-bug-tracker] [bug #59438] GUI debugger does not respect dbup, db


From: Richard
Subject: [Octave-bug-tracker] [bug #59438] GUI debugger does not respect dbup, dbdown to display current file in stack.
Date: Tue, 10 Nov 2020 05:34:24 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.75 Safari/537.36

URL:
  <https://savannah.gnu.org/bugs/?59438>

                 Summary: GUI debugger does not respect dbup, dbdown to
display current file in stack.
                 Project: GNU Octave
            Submitted by: crobar
            Submitted on: Tue 10 Nov 2020 10:34:22 AM UTC
                Category: GUI
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Feature Request
                  Status: None
             Assigned to: None
         Originator Name: Richard Crozier
        Originator Email: 
             Open/Closed: Open
                 Release: 5.2.0
         Discussion Lock: Any
        Operating System: Any

    _______________________________________________________

Details:

When debugging, if you navigate using dbup or dbdown to move around the call
stack, the GUI editor debugger does not open the same file and display where
you are in the stack in the editor. It still displays the last place in the
stack.

It would also be very helpful if the visual debugger would open the file at
the current position in the call stack when you navigate it. Similarly, a GUI
method of navigating the call stack would be nice, as is present in other
IDEs, including Matlab. In Matlab this is a simple drop down box where you can
select the desired position in the call stack. 

I have put this as a feature request, but I would suggest that not displaying
the current file in the editor is verging on being a bug.




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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