octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #58931] Right-clicking on a function name defi


From: Tasos Papastylianou
Subject: [Octave-bug-tracker] [bug #58931] Right-clicking on a function name defined as a command-line function to edit it leads to inconsistent behaviour
Date: Mon, 10 Aug 2020 13:04:44 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0

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

                 Summary: Right-clicking on a function name defined as a
command-line function to edit it leads to inconsistent behaviour
                 Project: GNU Octave
            Submitted by: tpapastylianou
            Submitted on: Mon 10 Aug 2020 05:04:42 PM UTC
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Regression
                  Status: None
             Assigned to: None
         Originator Name: Tasos Papastylianou
        Originator Email: 
             Open/Closed: Open
                 Release: 5.2.0
         Discussion Lock: Any
        Operating System: Any

    _______________________________________________________

Details:

Prompted by this question on stackoverflow:
https://stackoverflow.com/q/63325950/4183191

Steps to reproduce:
Step 1: Create the following script called myfunctiondefs.m


1;
function f1(); disp('hello from f1'); endfunction
function f2(); disp('hello from f2'); endfunction


Step 2: Create script myscript.m in the same directory


myfunctiondefs
f1()
f2()


Step 3: Open myscript.m in the octave GUI editor, run it once to generate the
function definitions in the current session, and then highlight "f2" with the
mouse, right-click, and select Edit f2 from the context menu.

Expected outcome: A generated f2.m file in the user's home folder, i.e. the
same as what would have happened if one manually typed "edit f2.m" in the
terminal.

Observed outcome: 
 - In octave v5.1.0: A popup window saying "f2 is a built-in, compiled, or
inline function and cannot be edited".

 - In octave v5.2.0: An empty, nameless m-file (in other words, a file called
".m" is created in the current directory).

Clearly there's a regression bug between v5.1.0 and v5.2.0. 

However, the bigger question is, when a name in the GUI editor is a reference
a command-line function, which doesn't right-clicking and selecting to edit it
behave the same as the equivalent "edit" command?




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]