On 09/07/09 03:15, Ben wrote:
>
> I haven't set showtabline, and I just tried reinstalling, and it
> didn't solve the problem.
>
> I have good news, however. I've discovered that if I start cmd.exe and
> don't do anything (i.e. don't set any new settings or run any
> command), and then cd to the vim directory ("C:\Program Files\Vim
> \vim72\") and run vim, then the problem disappears. The problem only
> shows itself after I've executed (seemingly) any executable command
> that was downloaded with cygwin. For example, if I type C:\bin\ls, and
> then run vim, the problem shows itself (and yes, I have installed
> cygwin on the root). Even if I start a new instance of cmd.exe from
> the same cmd shell, the problem still shows itself on subsequent vim
> runs. It's as if running any cygwin executable "contaminates" the
> shell, so that any subsequent vim run will exhibit this slightly
> inconvenient defect. I haven't been able to figure out what's the
> underlying cause of this, so any insight would be appreciated.
>
> Ben
What is the answer to
PATH
typed at the cmd promt (with no argument), before and after you run
\bin\ls? Is your current directory unchanged? Anything else that looks
weird in the answer to
SET
(again, with no arguments) before and after?
Best regards,
Tony.
--
The cure for boredom is curiosity. There is no cure for curiosity.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
