[Octave-bug-tracker] [bug #62931] Octave wrongly reports "error sourcing file" when there's a syntax error in a script with an extra '.' in the filename

[Richard Lobb]

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

                 Summary: Octave wrongly reports "error sourcing file" when
there's a syntax error in a script with an extra '.' in the filename
                 Project: GNU Octave
               Submitter: trampgeek
               Submitted: Sun 21 Aug 2022 09:19:41 AM UTC
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error or Warning
                  Status: None
             Assigned to: None
         Originator Name: Richard Lobb
        Originator Email: 
             Open/Closed: Open
                 Release: 6.4.0
         Discussion Lock: Any
        Operating System: GNU/Linux


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Sun 21 Aug 2022 09:19:41 AM UTC By: Richard Lobb <trampgeek>
With Octave 6.4.0 if you have a script called, say, junk.m with a syntax error
and you run it with

octave --no-window-system junk.m

you get the correct error message, e.g. "error: parse error near line 1 .."

But if you rename the file to, say, junk.1.m and try to run that you instead
get told

error: source: error sourcing file '<workingdir>/junk.1.m'

If there is no syntax error, the command works fine.

With version 5.2 of Octave you get both the expected syntax error report *and*
the 'error sourcing file' message.

Sample terminal dialogue with Octave 6.4:

blah:~$ cat >junk.m
x = 10(;
blah:~$ octave --no-window-system junk.m
error: parse error near line 1 of file /home/xxx/junk.m

  syntax error

>>> x = 10(;
           ^
blah:~$ cp junk.m junk.1.m
blah:~$ octave --no-window-system junk.1.m
error: source: error sourcing file '/home/xxx/junk.1.m'












    _______________________________________________________

Reply to this item at:

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

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