On 4/16/08, Erik Falor <[EMAIL PROTECTED]> wrote: > > On Wed, Apr 16, 2008 at 12:22 PM, Erik Falor <[EMAIL PROTECTED]> wrote: > > > > > On 4/13/08, Tony Mechelynck <[EMAIL PROTECTED]> wrote: > > > > > > > > > On 13/04/08 15:10, Andy Wokula wrote: > > > > Tony Mechelynck schrieb: > > > >> vim -gNu NONE > > > >> :set wildmenu wildmode=longest:full,full laststatus=2 > > > >> :lcd<Tab> > > > > > > > > Hmm, this works for me: Press<Tab> twice before using the arrow > > > keys. > > > > The first<Tab> just shows the menu without selecting an entry. It > > > > would be less confusing if the first entry wasn't highlighted > > > > immediately. > > > > > > > > > > > > > Doesn't work either. Normally I use <Right> rather than <Tab> until > > > the > > > right entry is both highlighted and filled-in but even with <Tab> > > > instead I still get a beep when I try to use <Down>. > > > > > > > > > Best regards, > > > Tony. > > > > > > -- > > > Silverman's Law: > > > If Murphy's Law can go wrong, it will. > > > > > > > > > > > > > > > > > FWIW, I can reproduce this on Windows with Vim 7.1 w/o any patches. > > More specifically, directories that show up in the wildmenu as a result > > of :e <Tab> let you use <Up> and <Down> to enter/exit them. > > Directories that show up in the wildmenu as a result of :lcd <Tab> do > > not work the same way. > > > > VIM - Vi IMproved 7.1 (2007 May 12, compiled May 12 2007 14:19:39) > > MS-Windows 32 bit GUI version with OLE support > > Compiled by [EMAIL PROTECTED] > > > > I see this same confusing behavior on Linux Vim 7.1.244: > > > > VIM - Vi IMproved 7.1 (2007 May 12, compiled Feb 7 2008 22:31:25) > > Included patches: 1-244 > > Compiled by [EMAIL PROTECTED] > > Normal version with GTK2 GUI. Features included (+) or not (-): > > > > Unfortunately I don't have an unpatched version of GTK2 > > Vim to play with :( > > > > -- > > Erik Falor > > Registered Linux User #445632 http://counter.li.org > > > I just had a thought: what if you define a custom command that uses > -complete=file and another that uses -complete=dir? Will they behave the > same? Do the built-in commands use the same code for their completion?
These are the results of testing my idea: complete_test.vim: ============== set history=0 wildmenu wildmode=longest:full,full laststatus=2 command -nargs=1 -complete=dir CompleteDir echo <args> command -nargs=1 -complete=file CompleteFile echo <args> ======EOF===== C:\Documents and Settings\efalor\Desktop>gvim -NU NONE -u complete_test.vim I just tried completing these two custom commands, and found that they do behave differently with regard to <Up> and <Down> keystrokes on a directory name. I checked this both on lately patched gvims on windows and linux, as well as the original 7.1 release of gvim.exe for windows. All three executables behaved the same. -- Erik Falor Registered Linux User #445632 http://counter.li.org --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
