[Octave-bug-tracker] [bug #53702] GUI editor break points use out-of-date line numbers when a file is modified

[Mike Miller]

Update of bug #53702 (project octave):

                Severity:              3 - Normal => 2 - Minor              
              Item Group:              Regression => Incorrect Result       
                  Status:               Need Info => Confirmed              
                 Summary: Debug points can't be set on some lines => GUI
editor break points use out-of-date line numbers when a file is modified

    _______________________________________________________

Follow-up Comment #3:

Ok, I do see what you are getting at, but all of these examples do work for me
if the file is closed in the editor, at least one command is entered in the
command window, or even just a blank line with Enter, and then the file is
reopened in the editor.

The GUI already tries to resynchronize the breakpoint state with the
interpreter, but apparently this requires at least one command or an Enter to
be done in the command window first.

I don't think this is a regression, and an easy workaround is available.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/