[Octave-bug-tracker] [bug #31080] User scripts or functions created during a session on Windows are not found

[Dennis Cote]

Follow-up Comment #87, bug #31080 (group octave):

[comment #84 comment #84:]
> @dennisc_hi: If you were able to consistently reproduce this error
> (independent on some time intervals), you were very likely seeing a different
> issue. 

I am able to consistently reproduce this error using Octave 9.3.0 on my
Windows 11 PC. It does not work sometimes and fail other times. 

I can't seem to get my Octave 10.0.0 (local MINGW64/MSYS2 build of mercurial
source) to fail, ever.

The version info for my Octave 9.3 is:

>> ver
----------------------------------------------------------------------
GNU Octave Version: 9.3.0 (hg id: 5854a65df8f5)
GNU Octave License: GNU General Public License
Operating System: MINGW32_NT-6.2 Windows 6.2  x86_64


The version info for my Octave 10.0 is:

>> ver
----------------------------------------------------------------------
GNU Octave Version: 10.0.0 (hg id: 00671f5dbc55+)
GNU Octave License: GNU General Public License
Operating System: MINGW32_NT-10.0 Windows 10.0  x86_64


They are built with different source files and it appears they are compiled
for different versions of the Windows OS.

I also noticed that my Octave 9.3 is executing several commands in my
C:\Users\DennisC\.octaverc file. One of these adds a second, explicit, path to
current directory, C:\Users\DennisC, in addition to ".".

EDITOR("notepad++.exe")
addpath("~")
addpath("~/Downloads")
pkg load control
pkg load signal


Interestingly, to verifying that the .octaverc file was adding the explicit
path to C:\Users\DennisC to the load path I renamed the .octaverc file to
hide.octaverc and restarted Octave 9.3.0. I verified the explicit path was not
listed on the load path. I then created a new script file and immediately
executed it without error. I repeated the test for a second function file and
it also worked correctly. After typing this, thinking the issue might be
related to the alternate load path, I repeated my test a third time and it
failed as before. I waited a while longer and created a fourth file and it
worked. I could also execute the third file at that point as well. So it
appears that my Octave 9.3.0 is inconsistent after all, contrary to my earlier
claim. I guess I was just unlucky in many previous tests.

I executed your test sequence with my Octave 10.0.0, creating a more than a
dozen new files and immediately executing them. I don't type too fast, so this
process took about 10-15 minutes. Every one of the files executed correctly. I
repeated once more after typing this and it also worked.

It seems to be fixed in Octave 10.0 with your patch.


    _______________________________________________________

Reply to this item at:

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

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

signature.asc
Description: PGP signature