On 2025-02-07, ubaldot (Vim Github Repository) wrote: > Yes, this seems so recurrent / common a problem with so many vimscript > work > arounds that in practice with the advent of Git it seems to me the more > useful option than &autochdir. > > Yeah, I think the better is to keep Vim as general as possible and with less > ties as possible to any specific external tool for which we have no control. > In > the future git may be replaced with something else, yet we would have to > maintain a git-related feature only for retro-compatibility reasons. Not a > smart move. External tools are better handled via plugins IMHO.
I agree. Even considering only git, if your project has submodules, the meaning of "project root" is ambiguous: do you mean the root of the current submodule or the top-level root of the entire project? Which you want depends on the situation. I've been working for years on a plugin that would allow Vim to know the root directory of whatever project it was in, whether using git, some other VCS, or no VCS. It's not easy to get the rules right, and I still have a file of exceptions to those rules. Regards, Gary -- -- 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. To view this discussion visit https://groups.google.com/d/msgid/vim_dev/20250207145749.GD10587%40phoenix.
