[Octave-bug-tracker] [bug #60990] Custom file editor not launched when clicking on link or selecting edit-at-line from gui

[Tasos Papastylianou]

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

                 Summary: Custom file editor not launched when clicking on
link or selecting edit-at-line from gui
                 Project: GNU Octave
            Submitted by: tpapastylianou
            Submitted on: Thu 29 Jul 2021 02:09:04 PM UTC
                Category: GUI
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error or Warning
                  Status: None
             Assigned to: None
         Originator Name: Tasos Papastylianou
        Originator Email: 
             Open/Closed: Open
                 Release: 6.3.0
         Discussion Lock: Any
        Operating System: GNU/Linux

    _______________________________________________________

Details:

Steps to reproduce:

1. Create a simple script containing a bug, which will trigger a typical
octave error, e.g. a script testo.m containing only the line "asdf;" will
trigger:


[octave prompt] testo
error: 'asdf' undefined near line 1, column 1
error: called from
    testo at line 1 column 1


2. The "testo at line 1 column 1" here is a clickable link (or, alternatively,
right click and select "Edit testo at line 1").

If you have not disabled the gui-editor, this should open the file at the
specified line in the built-in gui editor.

3. Now go to Edit -- Preferences -- Editor, tick "use custom file editor", and
specify an external editor of your choice, e.g. "gedit %f +%l".

4. Now click on the link again (or alternatively, right click and select "Edit
testo at line 1")

Expected result: Gedit editor should launch and open testo.m at line 1
Actual result: Nothing happens.

Notes: this happens with all editors tried, not just gedit bug. This includes
console editors like nano/vi. Also, the edit command within octave works as
expected, so this bug is exclusive to this 'clicking on an error link'
behaviour.




    _______________________________________________________

Reply to this item at:

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

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