I'm wondering whether not mentioning that 'path' can (should?) be set locally is intentional. I typically use `setlocal path=` on a per-filetype basis in `~/.vim/after/ftplugin` scripts.
I'm of two minds regarding that strategy. On one hand that is how I override filetype-specific stuff in general, and some of my after scripts are pretty large. On the other hand, I have found &path to be highly framework/stack dependent instead of filetype-specific, which lead me to replicate the same setting over several files, which I didn't really like. I've switched to a more "holistic" approach, where I set &path in my vimrc, to an exhaustive list of interesting directories typical of the kind of project I work on. The linked gist kind of reflects my position on this, but feel free to comment on it if you feel something is missing or wrong. -- -- You received this message from the "vim_use" 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_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/vim_use/fac95e14-dfa6-47e7-8eb9-559cbcec0d2en%40googlegroups.com.
