[Octave-bug-tracker] [bug #41278] "edit myFunction.m" does not work when it's read-only

[Mike Miller]

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
now.

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:

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

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