[Octave-bug-tracker] [bug #45967] More consistent error message style for parse errors

[Ceral Paquet]

URL:
  <http://savannah.gnu.org/bugs/?45967>

                 Summary: More consistent error message style for parse errors
                 Project: GNU Octave
            Submitted by: octavebugs
            Submitted on: Tue 15 Sep 2015 12:19:24 AM GMT
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.0.0
        Operating System: GNU/Linux

    _______________________________________________________

Details:

function myfoo()

i am a bug

endfunction


 
function mybar()

i_am_a_bug

endfuction


-----------------


>> myfoo
parse error near line 3 of file /home/ceral/octave/myfoo.m

  syntax error

>>> i am a bug
       ^

>> mybar
error: 'i_am_a_bug' undefined near line 3 column 1
error: called from
    mybar at line 3 column 1



Would it be possible to use the same style for these two types of error?
Perhaps the latter is slightly tidier. How about:

>> myfoo
error: syntax error near line 3 column 1
error: called from
    myfoo.m at line 3 column 1


What would be awesome is to have the final line be clickable and take you to
that file and line in the Editor.





    _______________________________________________________

Reply to this item at:

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

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