On 19 July 2010 03:14, Nazri Ramliy wrote: > On Mon, Jul 19, 2010 at 6:11 AM, Bram Moolenaar wrote: >> Björn Winckler wrote: >> >>> I built a new (MacVim) binary using the latest source and noticed that >>> command autocompletion is behaving strangely. > > [snip] > >> Looks like the new :find completion. It completes files that would be >> found when executing the ":find" command. Did you intend to use ":edit" >> instead?
I guess...I usually use ":f" instead of ":e" to avoid inadvertently opening a new buffer in case I mistyped the filename. >> >> The duplicates shouldn't be there, that's a bug. > > I'm the one to blame :) > > Björn, could you let me know what your 'path' setting is? :set path? path=.,/usr/include,, (Look at that -- another option I didn't know about! ;-) > > Just to be sure: did you really see two "appkit.h", and not "include/appkit.h" > and "appkit.h"? There's only one file. To double check I renamed the file "appkitborkborkbork.h" (I know for sure there is no other file called that on my filesystem) and I get :tabf ap apache2/ appkitborkborkbork.h applicatives.hs appkitborkborkbork.h applicatives.hs apr-1/ However, If I use :f the situation changes (I just noticed this)! :f app appkitborkborkbork.h applicatives.hs So it would seem the bug is in ":tabf" but not ":f". > > b.t.w: Thanks a lot for writing up the vim-hg-git guide . It is really useful > to me as I don't grok mercurial as good as I do git. I'm glad it is of use! Björn -- You received this message from the "vim_dev" 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
