Re: Opening editor from Octave command line

[Ben Abbott]

On Nov 12, 2012, at 5:40 AM, Nilson wrote:
> 
> Date: Thu, 8 Nov 2012 22:02:45 -0800
> From: [hidden email]
> To: [hidden email]
> Subject: Re: Opening editor from Octave command line
> 
>> Nilson wrote
>> I get the same answer when trying to edit a .m file. 
>> 
>> octave:> edit teste.m 
>> error: system: CreateProcess failed -- can't create child process 
>> error: called from: 
>> error: 
>> C:\Octave\Octave3.6.2_gcc4.6.2\share\octave\3.6.2\m\miscellaneous\edit.m at 
>> line 299, column 7 
>> 
>> Well, the OS I'm working with is Windows 7. 
>> I install the 3.6.1 and got the same weird thing. 
>> 
>> This type of error appeared only after reinstalling Windows 7 and Octave. 
>> 
>> So far it seems that no one can solve this problem. 
>> 
>> Do you have any suggestions that would be effective, please? 
>> 
>> Thanks in advance, 
>> 
>> Nilson
>> Please check whether your installed notepad++ is really on C:\Program 
>> Files\Notepad++\ (use windows explorer and try to locate this directory). 
>> If your windows 7 is a 64bit version, it has probably has been installed to 
>> C:\Program Files (x86)\Notepad++\ 
>> 
>> Nitzan 
>> 
>> If you reply to this email, your message will be added to the discussion 
>> below:
>> http://octave.1599824.n4.nabble.com/Opening-editor-from-Octave-command-line-tp4644606p4646301.html
>> To unsubscribe from Opening editor from Octave command line, click here.
>> NAML
> 
> Yeah, Nitzan, you're rigth, my windows 7 is a 64bit version and I'd changed 
> the octaverc file like this:
> ## Uncomment and change following line for your preferred editor
> EDITOR('C:\\Arquivos de Programas (x86)\\Notepad++\\notepad++.exe');
> 
> But it didn't work even so!
> 
> Nilson 

I experimented with using gvim with Octave 3.6.2 on Win7 yesterday.  For gvim 
to work, I added the following the ~.octaverc

        edit editor "gvim %s"
        edit mode sync

On Linux and MacOS, I use "async", that Win7 threw an error.  However, with 
"sync" the editing does work an the "async" manner.

Ben