[Octave-bug-tracker] [bug #46281] newly defined private functions are inaccessible until restart of octave session

[Tasos Papastylianou]

Follow-up Comment #8, bug #46281 (project octave):

Hi Pantxo.
I am also on Linux Mint 17.2.
Could you post your m-file here to cross-check?

In the process of writing an .m file for you as a testcase, I realised that
this issue (bizarrely) does not occur if these commands are run as a script,
or as the whole thing copy/pasted onto the terminal. But if you run them one
by one on the terminal it will happen.

Did you by any chance perform the console test by simply pasting over the
contents of your entire script on the terminal and pressing enter?

Could you try running the commands in my .m file one-by-one (e.g. by pressing
F9) and see if you can reproduce the issue?

This is very bizarre ... then again, this wouldn't be the first time you get a
different result running commands as a batch compared to individually. (I had
a similar experience trying to set figure visibility off/on, as a workaround
for the broken shg command - it works if you do this on the console one by
one, but just doesn't happen if you run these commands in a script)

T.


(file #35280)
    _______________________________________________________

Additional Item Attachment:

File name: privatetest.m                  Size:0 KB


    _______________________________________________________

Reply to this item at:

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

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