I am running vim 7.3.659 on a 64-bit Arch Linux system. I am seeing what I believe to be a bug in the filename-completion logic as used in the :buffer command. To reproduce, do the following:
1. mkdir /tmp/foo 2. cd /tmp/foo 3. Somehow, create two files in /tmp/foo -- foo.c and bar.c. 4. Start vim. Enter ':e bar' followed by <tab>. It will complete to 'bar.c'. Hit <enter> to load the file. Do the same for foo.c. Note that after typing ':e foo' and then <tab>, it will complete to 'foo.c'. 5. You will have foo.c displayed in the vim window. If you enter ':b ba' followed by <tab>, it will complete to 'bar.c'. Hit <enter>. Now the window displays bar.c. Now type ':b fo' followed by <tab>; it will not complete. But if you hit <enter> at that point, the window will switch correctly to foo.c. I think the logic is getting confused by the directory name and the filename both being 'foo'. If you move the directory to /tmp/baz, the problem will not occur. My .vimrc: set shiftwidth=4 set tabstop=4 set incsearch set wildmode=longest set autoindent set lispwords=define,let,let*,do,lambda,case let g:yankring_persist = 0 let g:yankring_share_between_instances = 0 let g:yankring_history_dir = '$VIM' set nocp filetype on filetype plugin on let g:sqlutil_align_where = 0 let g:sqlutil_align_comma = 1 map <f2> :NERDTree<CR> /Don Allen -- 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
