On Tue, Feb 9, 2010 at 6:18 PM, Caomai <[email protected]> wrote:
> Now a somewhat different error occurs which appears to happen after a > call to the Windows API. > "WindowsError: [Error 2] The system cannot find the file specified" > > gvim does not launch in this situation either. gvim is in my system > PATH and can be launched from a standard cmd shell using "gvim" > without preceding path. > > # Try: LEO_EDITOR="C:\Program Files (x86)\Vim\vim72\gvim.exe" > Result: "WindowsError: [Error 5] Access is denied." > > # Try: LEO_EDITOR=C:\PROGRA~2\Vim\vim72\gvim.exe > Result: Success [snip] > My take on this is that the path+name of the specified editor (in > either LEO_EDITOR or EDITOR) cannot have BLANKS in the path when the > executable needs to be searched for and cannot use QUOTES when > specifying the complete path (which is a common Windows convention for > path+file with blanks). Correct. I'm not sure whether this can be fixed. There are comments to this effect in c.openTempFileInExternalEditor that pertain to the 'os.system' way of specifying actions. Is this what you are using? If so, maybe using another way would work. Or maybe this is just a documentation issue. After all, you have found ways to get the job done. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
