On 25/09/09 20:53, Bram Moolenaar wrote:
> Dalfa Zen wrote:
>> Hello everyone,
>> I don't know if this has already been done
>> I use "vim72d32.zip" to install vim in my freedos.
>> When finish install, back to the root C:\ run "C:\> vim"
>> But it can't work, the Command-line display this "c:\vim72\vim.exe
>> not found".
>> Then I look at c:\fdos\bin\vim.bat, I found some mistakes.
>> I think this 4 lines is wrong in the vim.bat :
>> line 5: if exist "%VIM%\vim72\vim.exe" set VIM_EXE_DIR=%VIM%\vim72
>> line 6: if exist "%VIMRUNTIME%\vim.exe" set VIM_EXE_DIR=%VIMRUNTIME
>> %
>> line 8: if exist "%VIM_EXE_DIR%\vim.exe" goto havevim
>> line 9: echo "%VIM_EXE_DIR%\vim.exe" not found
>> Change them into :
>> line 5: if exist %VIM%\vim72\vim.exe set VIM_EXE_DIR=%VIM%\vim72
>> line 6: if exist %VIMRUNTIME%\vim.exe set VIM_EXE_DIR=%VIMRUNTIME%
>> line 8: if exist %VIM_EXE_DIR%\vim.exe goto havevim
>> line 9: echo %VIM_EXE_DIR%\vim.exe not found
>> Just take out the quote. it works :)
> I haven't verified, but I think taking out the quotes breaks it for when
> Vim is installed below a directory that conains a space.
> I think the problem is with the freedos batch program.
Does freedos support Long File Names? If it doesn't, then no paths can
contain spaces and the quotes are not necessary (nor can the command
interpreter -- COMMAND.COM, maybe -- be expected to support them).
OTOH, if freedos _does_ support Long File Names, then its command
interpreter ought to accept quoted paths -- but maybe some startup
setting is needed for that?
Best regards,
Tony.
--
PISCES (Feb. 19 to Mar. 20)
Take the high road, look for the good things, carry the
American Express card and a weapon. The world is yours today, as
nobody else wants it. Your mortgage will be foreclosed. You will
probably get run over by a bus.
|
