Closed adriansm closed 5 years ago
Thanks for the contribution! I think this needs a specification discussion. Where the .editorconfig files are located should be consistent across editors. I'll ask around.
I don't think we should follow symlinks in the Vim, as this is consistently not followed in other core libraries. In your case, my suggestion is to add a quick file list in Vim so that you can quickly let Vim open these files directly, instead of vim /path/to/symlink
.
This can also be solved with something like: https://stackoverflow.com/questions/30791692/make-vim-follow-symlinks-when-opening-files-from-command-line
However it seems more obvious to me to allow files to follow editorconfig options from the real location of file. That being said, agree that this should be consistent across editors
There are pros and cons for either approach. Thanks for your contribution and will close this now for the sake of consistency.
When linking files, the final file may be somewhere else where there may be an .editorconfig file.
Example: ~/.gitconfig -> ~/dotfiles/git/config
By following symlinks, in this example the .editorconfig can remain at ~/dotfiles/git/.editorconfig