|
From: | Torsten |
Subject: | [Octave-bug-tracker] [bug #40600] edit: changing EDITOR after first call to edit() has no effect |
Date: | Sat, 23 Nov 2013 23:00:16 +0000 |
User-agent: | Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 |
Follow-up Comment #7, bug #40600 (project octave): EDITOR () is more or less _not_ used for edit () (only for the very first initialization). Changing the EDITOR-field in edit has to be done by edit EDITOR "some_editor" not by using EDITOR () which only changes the editor used for edit_history. So maybe we should leave things here as they are and clarify this in the docs. But I agree that it is confusing that the GUI editor or a custom editor configured in the GUI is called when edit () is evaluated regardless the EDITOR field of edit. I submitted a patch #8240 that synchronizes the editor configuration of edit () and of the GUI. Maybe it helps avoiding this confusion. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?40600> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |