Sorry, I realize I forgot a key piece of information -- I'm not using
cygwin's vim 7.2, I'm using vim 7.2 as downloaded from http://www.vim.org/
(the PC: MS-DOS and MS-Windows version). So perhaps the problem is
with vim.org's version and not cygwin's version?

Anyway, I tried all three commands and they all produced the same
error as before when using vim (and gvim still succeeded with all
three commands).

Ben

On Jul 3, 3:49 pm, Matt Wozniski <[email protected]> wrote:
> On Fri, Jul 3, 2009 at 2:11 AM, bgold12 wrote:
>
> > I've found that when I type "gvim a" from the command line, I get a
> > message in the status line after gvim has started up that gives some
> > info about the file a. For example, if the file doesn't exist, it says
> > ""a" [New File]"; if the file does exist but is empty, it says ""a"
> > 0L, 0C".
>
> > This is a very nice feature, but it doesn't seem to work with vim (as
> > opposed to gvim). From what I can tell, the message IS displayed with
> > vim, but it disappears after a fraction of a second.
>
> > I know I can get similar info by typing CTRL-G, but obviously it would
> > be better if I didn't have to do that every time I open a file.
>
> > So, is this a bug in vim, or a problem with my settings, and if the
> > latter, how can I fix this? If it's important, I'm running Windows XP,
> > vim 7.2, and I'm using cygwin (bash) as my command line.
>
> > Thanks,
>
> > Ben
>
> Well, I can't reproduce this problem cygwin's vim 7.2, neither in
> cmd.exe nor in mintty nor in xterm.  So, let's try some basic
> troubleshooting.  First things first,
>
>     vim -u NONE -N a
>
> will disable all vimrcs and plugins.  If it works there, then try both
>
>     vim -u NORC -N a
>
>     vim --noplugin -N a
>
> If one of those works and the other doesn't, then it tells you that
> either a vimrc is the problem, or that a plugin is the problem.  Then,
> report back and we might be able to pin down exactly what's going
> wrong.
>
> ~Matt
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to