If there is only a problem with :Ex and not with :e, then I was
barking up the wrong tree.  I think you are right:  the definition of
:Explore has changed, and that is why command-line completion does not
work.  I am cc'ing the author of the netrw plugin, so he can fix it.

     Here is the definition of :Explore from vim 6.4
(plugin/explorer.vim):

  command -n=? -complete=dir Explore :call s:StartExplorer(0, '<a>')

Here is the definition from vim 7.0 (plugin/netrwPlugin.vim):

com! -nargs=? -bar -bang -count=0       Explore         call 
netrw#Explore(<count>,0,0+<bang>0,<q-args>)

Note the missing "-complete=dir".

HTH                                     --Benji Fisher

On Fri, May 12, 2006 at 08:12:00AM -0700, inet working wrote:
> i did a little more research and it seems <tab>
> completion *only* doesn't work for ":Ex LongDir<tab>".
> 
> If i just do :e LongDirTo<TAB> or in many other cases,
> tab filename completion works just fine.  I am
> guessing ":Ex" directory explorer is diff from prev
> versions so the default tab completion behavior in
> cmdline mode changed while more features are added to
> the implementation of cmdline-completion and/or ":Ex"
> dir explorer, since :Ex cmdline is taking wildcards
> for pattern matching, like :Ex *foobar.
> 
> The output for your suggested commands in my gvim7 on
> winxp seems to be pretty reasonable - what do you
> think? Thanks.
> 
> output of :verbose set compatible? cpo? wildchar?
> 
> nocompatible
>       Last set from C:\Program
> Files\Vim\vim70\vimrc_example.vim
>   cpoptions=aABceFs
>       Last set from C:\Program
> Files\Vim\vim70\autoload\netrw.vim
>   wildchar=<Tab>
>       Last set from C:\Program
> Files\Vim\vim70\vimrc_example.vim
> 
> output of :scriptnames
>   1: C:\Program Files\Vim\_vimrc
>   2: C:\Program Files\Vim\vim70\vimrc_example.vim
>   3: C:\Program Files\Vim\vim70\syntax\syntax.vim
>   4: C:\Program Files\Vim\vim70\syntax\synload.vim
>   5: C:\Program Files\Vim\vim70\syntax\syncolor.vim
>   6: C:\Program Files\Vim\vim70\filetype.vim
>   7: C:\Program Files\Vim\vim70\menu.vim
>   8: C:\Program Files\Vim\vim70\autoload\paste.vim
>   9: C:\Program Files\Vim\vim70\ftplugin.vim
>  10: C:\Program Files\Vim\vim70\indent.vim
>  11: C:\Program Files\Vim\vim70\mswin.vim
>  12: C:\Program Files\Vim\vim70\colors\peachpuff.vim
>  13: C:\Program Files\Vim\vim70\plugin\getscript.vim
>  14: C:\Program Files\Vim\vim70\plugin\gzip.vim
>  15: C:\Program Files\Vim\vim70\plugin\matchparen.vim
>  16: C:\Program Files\Vim\vim70\plugin\netrwPlugin.vim
>  17: C:\Program Files\Vim\vim70\plugin\rrhelper.vim
>  18: C:\Program Files\Vim\vim70\plugin\spellfile.vim
>  19: C:\Program Files\Vim\vim70\plugin\tarPlugin.vim
>  20: C:\Program Files\Vim\vim70\plugin\tohtml.vim
>  21: C:\Program
> Files\Vim\vim70\plugin\vimballPlugin.vim
>  22: C:\Program Files\Vim\vim70\plugin\zipPlugin.vim
>  23: C:\Program Files\Vim\vim70\scripts.vim
>  24: C:\Program Files\Vim\vim70\autoload\netrw.vim
>  25: C:\Program Files\Vim\vim70\syntax\netrw.vim
>  26: C:\Program Files\Vim\vim70\syntax\help.vim
>  27: C:\Program Files\Vim\vim70\ftplugin\help.vim
> 
> --- Benji Fisher <[EMAIL PROTECTED]> wrote:
> 
> > On Thu, May 11, 2006 at 09:27:25AM -0700, inet
> > working wrote:
> > > I just installed vim7 on windows xp. the installer
> > > prog also removed vim6 (i chose to keep the vimrc
> > file
> > > i'd). 
> > > 
> > > first problem i ran into is, in gvim command mode,
> > > typing
> > > :Ex c:\LongDir<TAB>
> > > 
> > > insert ^I instead of completing the file/dir name
> > to
> > > LongDirName.  This always worked until vim7. 
> > > 
> > > Do I (how) need to edit .vimrc somehow so tab file
> > > name completion would work again in Vim7 ? 
> > 
> >      It looks as though you are getting
> > vi-compatible behavior of <TAB>
> > on the command line.  Specifically, 'wildchar' may
> > be set to its
> > vi-default rather than its vim-default.  Please
> > check the following.
> > 
> > :verbose set compatible? cpo? wildchar?
> > 
> > You are supposed to get 'nocompatible' and
> > vim-defaults as soon as vim
> > finds a user vimrc file, so please also check that
> > your vimrc file is
> > being loaded by looking at
> > 
> > :scriptnames
> > 
> > HTH                                 --Benji Fisher
> > 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 

Reply via email to