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
On Jul 8, 1:23 am, Jay Heyl <[email protected]> wrote:
> On Tue, Jul 7, 2009 at 9:02 PM, Ben <[email protected]> wrote:
> > Just to reiterate an important point, I'm not running cygwin's vim
> > (which apparently doesn't have this problem), I'm running the vim that
> > came with the "Self-installing executable" from <http://www.vim.org/
> > download.php>. I think it may be a bug in that particular version of
> > vim, but I'm not sure.
>
> I'm using the same version as you on two different computers and have
> not seen the problem you're having. I just installed the latest
> version on this computer a couple days ago. When I run vim from a
> console window I see the standard screen you described.
>
> Maybe you should try reinstalling.
>
> -- Jay
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
