The RIDE User Guide has a section (8.2.1) on the RIDE_EDITOR configuration parameter that reads "The fully-qualified path to the executable of the editor to use in a Dyalog Session instead of the RIDE's built-in editor (for example, vim, Emacs or Notepad++)." This needs to be enhanced to include the info in the following email chain:
VINCE: I can get it to work by using gedit (as mentioned by Jay in fixed issue [0000413]), but not /usr/bin/vim. Does it have to be a window-y editor?
JAY: Yes I think it has to be a window-y editor -- or perhaps a script that knows how to launch an editor running in a new terminal window.
[Ported from Mantis 0017234]
The RIDE User Guide has a section (8.2.1) on the RIDE_EDITOR configuration parameter that reads "The fully-qualified path to the executable of the editor to use in a Dyalog Session instead of the RIDE's built-in editor (for example, vim, Emacs or Notepad++)." This needs to be enhanced to include the info in the following email chain:
VINCE: I can get it to work by using gedit (as mentioned by Jay in fixed issue [0000413]), but not /usr/bin/vim. Does it have to be a window-y editor?
JAY: Yes I think it has to be a window-y editor -- or perhaps a script that knows how to launch an editor running in a new terminal window.