Comment #5 on issue 79 by brammool...@gmail.com: Use 'path' setting for
filename completion (compl-filename)
https://code.google.com/p/vim/issues/detail?id=79
This feature is most useful to expand header files, without knowing where
they are:
#include "foo
In that situation we don't want
Comment #4 on issue 79 by chrisbr...@googlemail.com: Use 'path' setting for
filename completion (compl-filename)
https://code.google.com/p/vim/issues/detail?id=79
Thanks for your contribution. It's appreciated. Note, that vim develops
slowly and the main focus is fixing bugs. Considering th
Comment #3 on issue 79 by pawel.pa...@gmail.com: Use 'path' setting for
filename completion (compl-filename)
https://code.google.com/p/vim/issues/detail?id=79
During testing I spotted "unexpected" behavior. When `path` contains more
than one entry, for absolute entries, instead of completio
Comment #2 on issue 79 by pawel.pa...@gmail.com: Use 'path' setting for
filename completion (compl-filename)
https://code.google.com/p/vim/issues/detail?id=79
My first contribution, so what next steps are required to actually accept
this patch ? Should I write some unit tests ? Ask for revi
Comment #1 on issue 79 by pawel.pa...@gmail.com: Use 'path' setting for
filename completion (compl-filename)
https://code.google.com/p/vim/issues/detail?id=79
(No comment was entered for this change.)
Attachments:
ctrlx_ctrlf_path_search.patch 409 bytes
--
You received this message
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 79 by dhah...@gmail.com: Use 'path' setting for filename
completion (compl-filename)
http://code.google.com/p/vim/issues/detail?id=79
The help for i_CTRL-X_CTRL-F states:
"Note: the 'path' option is not used here (yet)."
