[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #57121] [GUI] debug pointer position off by on
From: |
Philip Nienhuis |
Subject: |
[Octave-bug-tracker] [bug #57121] [GUI] debug pointer position off by one line |
Date: |
Sun, 27 Oct 2019 16:42:32 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 |
Follow-up Comment #3, bug #57121 (project octave):
@Torsten: I made a typo, sorry.
Try to put the breakpoint at L.459 (line after the "else"). Setting it at
L.460 "if (looks_like_pkg_name)" works fine here as well.
I see it on Windows and on Linux, only in the GUI (didn't try the CLI).
AFAICS it's just that the pointer is off by one line.
I also saw it in other (private) functions of pkg.m but the pkg.m case is very
reliably reproducible here.
FWIW, I saw more behavior that is non-conformant: sometimes when I adapt code
and save the function to disk, followed by "clear -f", the changes aren't
picked up and I have to restart Octave. I'm used to private functions needing
"clear -f" before changes are picked up; but that even then changes are
ignored was new.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?57121>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #57121] [GUI] debug pointer position off by one line, Philip Nienhuis, 2019/10/27
- [Octave-bug-tracker] [bug #57121] [GUI] debug pointer position off by one line, Torsten Lilge, 2019/10/27
- [Octave-bug-tracker] [bug #57121] [GUI] debug pointer position off by one line, Rik, 2019/10/27
- [Octave-bug-tracker] [bug #57121] [GUI] debug pointer position off by one line,
Philip Nienhuis <=
- [Octave-bug-tracker] [bug #57121] [GUI] debug pointer position off by one line, Torsten Lilge, 2019/10/27
- [Octave-bug-tracker] [bug #57121] [GUI] debug pointer position off by one line, Rik, 2019/10/27
- [Octave-bug-tracker] [bug #57121] lexer counts lines incorrectly for block comments that immediately follow line comments, John W. Eaton, 2019/10/28
- [Octave-bug-tracker] [bug #57121] lexer counts lines incorrectly for block comments that immediately follow line comments, John W. Eaton, 2019/10/28
- [Octave-bug-tracker] [bug #57121] lexer counts lines incorrectly for block comments that immediately follow line comments, Philip Nienhuis, 2019/10/28
- [Octave-bug-tracker] [bug #57121] lexer counts lines incorrectly for block comments that immediately follow line comments, Rik, 2019/10/28