[Octave-bug-tracker] [bug #44880] Allow the Exec key in the desktop file to launch a script file

[Carnë Draug]

Follow-up Comment #7, bug #44880 (project octave):

> What I don't want is to click on the "GNU Octave" icon in my GNOME deskop
Applications menu and have it start Octave with the editor tab open.

Oh! So what you are trying to avoid is that it starts on the editor tab (vs
starting on the GUI console) and not that it starts the GUI (vs starting the
GUI)?

Took me a while to figure this out, so I'm writing it down all:

The desktop files controls both the action to open m files and to
start Octave from the main menu.  This needs to be the same
command.

Currently, the desktop entry uses '--gui %f'.  From the applications
menu, this starts the GUI on the console tab and persists (because %f
is empty).  From double clicking a file, it executes %f and then exit
the GUI.

Changing to '--gui --persist %f' will not change the start from the
application menu.  When double clicking on a file, it would execute %f
and then keep the Octave window open on the console tab.  However, %f
will not even be appear in the editor tab.  There would be no clue
that %f actually got executed.

Changing to '--gui --persist --edit "edit %f"' would make start from
the applications menu on the editor tab instead of the console tab.
It would make double click on a file open the editor tab and not
execute the file at all.

---

I think what we really need is that 'octave --gui %f' will implicit
open the editor if %f is not empty.  This would even add support for
%F (multiple files).

    _______________________________________________________

Reply to this item at:

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

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