[Octave-bug-tracker] [bug #50347] Refer command-line functions to their point of definition in an octave session when the 'which' command is used

[Tasos Papastylianou]

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

                 Summary: Refer command-line functions to their point of
definition in an octave session when the 'which' command is used
                 Project: GNU Octave
            Submitted by: tpapastylianou
            Submitted on: Sat 18 Feb 2017 03:02:28 AM UTC
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Feature Request
                  Status: None
             Assigned to: None
         Originator Name: Tasos Papastylianou <poacheR>
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.2.0
        Operating System: Any

    _______________________________________________________

Details:

As per
http://stackoverflow.com/questions/15260023/how-to-see-function-body-in-gnu-octave,
there is no way to refer back to the correct definition of a command-line
function in an octave session (let alone dump its definition in the
terminal).

Ideally, one should obtain the filename and line where it is defined (or the
line of the interpreter for the current session)  when querying it with the
"which" command, as for normal functions.

i.e.


octave:1> function y=f(x); y=x; endfunction
octave:2> which f
  'f' is a command-line function, defined on line 1 in the interpreter






    _______________________________________________________

Reply to this item at:

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

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