Wednesday, November 3, 2010

gvim behaves differently when starting from command-line and windows explorer

Hi buddies,
I usually worked on windows. Sometimes I opened a text file in the
command line (cygwin) by typing "gvim <file-name>". And sometimes I
open a file by right-clicking and choosing 'GVIM'.

And I found they are different! For example if a open a perl script
in the command line, there is such error message:
-----------------------------------------------------------------------------------
"spdb_build_report.pl" 945L, 29286C
Error detected while processing C:\bin\dev\Vim\vim73\ftplugin\perl.vim:
line 48:
E484: Can't open file C:\Documents and Settings\caogui\VIo3F.tmp
Error detected while processing function <SNR>9_LoadFTPlugin:
line 17:
E170: Missing :endfor
Error detected while processing function <SNR>8_FTpl:
line 10:
E171: Missing :endif
Press ENTER or type command to continue
-----------------------------------------------------------------------------------

But if I open it in the windows explorer, everything goes all right.


Why are they different?

Thanks:)


---------------------------------
( Dennis Cao )

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

No comments: