Nazri Ramliy wrote: > On Fri, Feb 20, 2009 at 9:18 AM, Nazri <[email protected]> wrote: >> I'm refining the patch - fixing a memory leak (stupid me :), and >> improving the shortening of the matching paths to get the minimum >> unique length of each. This is much much better than the simple (and >> not necessarily correct all the time) "relative to your working >> directory" or "home directory". The old method just won't work if your >> path setting does not include your home directory. The new method can >> produce sufficiently short paths to be comfortably seen on the >> wildmenu. > > Here's the improved patch. > > There's one major outstanding issue that I'm aware of - it does not > skip symbolic links. This may result in infinite cycle if there exists > a symbolic link that creates a cycle in the file system. > > I don't have access to a windows platform so I can't test the patch on > windows. It may have problems with those different drive letters. > > nazri.
Hi Nazri I'm trying your patch on Linux x86 (from Vim-7.2.108). I notice something broken. I do: $ mkdir foobar/ $ vim -u NONE set nocompatible set wildmode=longest,list set wildmenu set path=. If I type: :find foo<tab> I would expect to complete up to foobar/ (it does that without patch) but after patch it does not complete the directory name anymore. Cheers -- Dominique --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
