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

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

[Octave-bug-tracker] [bug #54737] confusion about startup dir and file b


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #54737] confusion about startup dir and file browser initial directory
Date: Wed, 26 Sep 2018 12:55:46 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

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

                 Summary: confusion about startup dir and file browser initial
directory
                 Project: GNU Octave
            Submitted by: jwe
            Submitted on: Wed 26 Sep 2018 04:55:45 PM UTC
                Category: GUI
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Documentation
                  Status: None
             Assigned to: None
         Originator Name: jwe
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

The "general" and "file browser" tabs in the settings dialog both have items
for "Startup path".  This is a bit confusing.  A new user might think that
that it is the directory where the startup.m file is located.  Or that both
settings refer to the same thing.  Maybe it would help to have the "file
browser" setting labeled as "initial file browser directory" and the "general"
setting to be "initial working directory for Octave interpreter"?

It might also help to explain why it is not possible to specify the initial
directory for the file browser if the checkbox for "Synchronize Octave working
directory with file browser" is selected.





    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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