[Octave-bug-tracker] [bug #44298] GUI Ctrl+O opens in wrong directory

[Dan Sebald]

Follow-up Comment #2, bug #44298 (project octave):

It seemed to me that the current behavior is for the editor uses the path of
the currently active file/tab.  There's a certain logic to that and sometimes
it is advantageous, but I agree that probably isn't as good as using pwd.  I
often run "edit xyz" where xyz is a library M-script, which places the ced in
some system directory somewhere, which isn't where I'd want to open a new
file.

In file-editor.cc I see:


  file_editor_tab *fileEditorTab = new file_editor_tab (ced);


where ced is the "current editor directory".

The problem with the pwd() connection is how to get pwd()?  There are many
features that would be easy to deal with if there were a mechanism for getting
the result of a command from the worker process (i.e., Octave core).

    _______________________________________________________

Reply to this item at:

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

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