[Octave-bug-tracker] [bug #65623] New Script Failing to Load - Only Workaround to Restart Octave

[anonymous]

URL:
  <https://savannah.gnu.org/bugs/?65623>

                 Summary: New Script Failing to Load - Only Workaround to
Restart Octave
                   Group: GNU Octave
               Submitter: None
               Submitted: Mon 22 Apr 2024 03:42:45 AM UTC
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error or Warning
                  Status: None
             Assigned to: None
         Originator Name: Rob
        Originator Email: vannirob000@gmail.com
             Open/Closed: Open
                 Release: 9.1.0
         Discussion Lock: Any
        Operating System: Microsoft Windows
           Fixed Release: None
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Mon 22 Apr 2024 03:42:45 AM UTC By: Anonymous
Sometimes, when I create a new script and save it in the current directory,
then call it in the command window, it will state that the call for the script
is undefined at line1 column1. This usually happens after already working in
Octave and then creating and saving a new script in the working directory. 

For troubleshooting, I have confirmed the file is in the load path, in current
directory, and does not contain any spaces or prohibited characters, so
there's no parsing errors. It's just failing to 'see' the file to load. I have
tried different file names and it does not work. When the error does occur, it
fails to load any new script and gives the error, "undefined at line1
column1". 

I did some research and found this article
(https://lists.gnu.org/archive/html/help-octave/2009-03/msg00212.html), but
rehash, clear all, and clearing the script name I'm attempting to load do not
work. 

The only solution is to restart Octave, and then my call to the script works
as it should. 

As a workaround restarting Octave each time does work, but it's a minor
inconvenience to have to restart Octave every time this happens. 

Any guidance is much appreciated.  

System: Windows 10

GNU Octave, version 9.1.0

Any guidance is much appreciated. 







    _______________________________________________________

Reply to this item at:

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

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