[Top][All Lists]

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

[Octave-bug-tracker] [bug #41278] "edit myFunction.m" does not work when

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #41278] "edit myFunction.m" does not work when it's read-only
Date: Thu, 14 Mar 2019 22:34:21 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36

Update of bug #41278 (project octave):

                  Status:             In Progress => Ready For Test         


Follow-up Comment #11:

I pushed two further changes to fix the edit function when its HOME setting is
empty or references a directory that doesn't exist, and then to change the
default to be unset and require the user to opt in to it.

* https://hg.savannah.gnu.org/hgweb/octave/rev/b09941690b65
* https://hg.savannah.gnu.org/hgweb/octave/rev/5ef01ab5c9e5

This should fix the remaining issues here and make the edit function behave
much more intuitively by default.

I've thought for a long time that this "copy read-only files into ~/octave"
feature was a little too magical to be the default, very glad that it isn't

I did not add a warning, but I did take a cue from Julien's comment #5, so now
if "editinplace" is set to false but "home" is set to a directory that doesn't
exist (e.g. if ~/octave doesn't exist), edit will edit in place anyway.


Reply to this item at:


  Message sent via Savannah

reply via email to

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