[Octave-bug-tracker] [bug #65548] Every time a new function is created in a separate m-file, an 'undefined' error message is displayed

[Markus Mützel]

Follow-up Comment #5, bug #65548 (group octave):

Thanks for the pointer.

I don't see immediately what could be wrong with that. But everything
load_path seems to be able to surprise me in one way or the other...

Found another way to work around the issue: Set a breakpoint in some line of
the script (e.g., by clicking at that line in the left side bar) after it was
saved but before executing it the first time with F5. In this case, the script
starts executing and stops at the breakpoint as expected. It continues to be
found on the load path also after the breakpoint is removed.

Is there a pattern? What happens to the load path when a function is executed
from the command window and a break point is added to a new function (but not
otherwise?)?



    _______________________________________________________

Reply to this item at:

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

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