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

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

[Octave-bug-tracker] [bug #40600] edit: changing EDITOR after first call


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #40600] edit: changing EDITOR after first call to edit() has no effect
Date: Sat, 23 Nov 2013 22:38:33 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.57 Safari/537.36

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

The confusing bit is that EDITOR is used for more than just the edit()
command.

EDITOR also supports edit_history(), which *must not* be an "asynchronous"
command or else it serves no purpose. In other words, if we want to keep
edit_history() (similar to the Unix "fc" command) then EDITOR must block until
the file is saved and the editor exits. On the other hand, for the edit()
command it is very useful (and now the default) to use an asynchronous editor
that comes up in a window and returns control to the Octave shell
immediately.

For example, my EDITOR is "vim" and "edit get editor" is "gvim %s".

It's probably true that edit() is used much more than edit_history(), and for
GUI users the interactive history panel will be much more useful, but until we
deprecate or remove edit_history(), we have this other use of EDITOR to keep
in mind.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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