[Octave-bug-tracker] [bug #40600] edit: changing EDITOR after first call to edit() has no effect

[Mike Miller]

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

The edit function was one of the first things I looked at when I started
contributing to Octave. I got confused quickly with the hierarchical
preferences and permutations and gave up on it after a while.

I may still have a patch somewhere that addressed this one, I'll try to find
it. I think the consensus was that the default should match EDITOR, but still
allow them to be changed independently. I think my patch did something like
initialize the persistent value inside edit to an empty matrix. When the
function is called, if the value is empty, use the value of EDITOR, else use
the persistent value. This would allow edit to track EDITOR if EDITOR is
changed, but also allow edit to use a different editor if desired.

They should be allowed to be different, for example I would want EDITOR to be
"vim" for editing history in the console, but I would want the edit function
to launch "gvim" and return control to the Octave shell.

    _______________________________________________________

Reply to this item at:

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

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