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

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

[Octave-bug-tracker] [bug #54718] __run_test_suite__ doesn't preserve st


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #54718] __run_test_suite__ doesn't preserve start or working directory
Date: Thu, 27 Sep 2018 09:19:31 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

Follow-up Comment #18, bug #54718 (project octave):

One more observation and question:

Currently, if you have the setting enabled, it appears that the Octave's
working directory is updated any time the file browser switches to a new
directory.  AND the file browser follows any change in Octave's working
directory.  That seems reasonable to me as long as they are always kept in
sync.

However,, if you have the setting disabled and the file browser becomes out of
sync with Octave's current working directory and then you enable the setting,
which one should change?  Should the file browser be reset to Octave's working
directory or should Octave's working directory be modified to match the file
browser?  It's not clear to me which should happen.  So maybe it is best to
just leave it out of sync until the user changes one of them.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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