On Wednesday, September 11, 2013 6:36:28 PM UTC+2, ZyX wrote: > > But let us assume for a moment that this behaviour is correct. Then: > > > > > > :buffer bar<CTRL-D> > > > > > > should display analogous results (because 'bar' is a substring in the > > > absolute path for all files). That is: > > Not only a substring, but it also starts one component of a path. This should > be the reason.
Ok, it makes sense. But what about the first part of my post, before "But let us assume for a moment that this behaviour is correct"? There is neither buffer named '~/foobar/bar' nor '~/foobar/baz'. There are only 'bar' and 'baz' buffers. The results returned by either ':ls' or '<CTRL-D>' are incorrect. It is very annoying while working with my current project. ':ls' returns buffers names relative to the root folder of my project but '<CTRL-D>' or 'TAB' (with 'wildmenu' enabled) sometimes (as in described scenario) distracts me with very long, unreadable absolute paths. -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.