![]() make sure that all editor configs are equally easy to discover,.I’m just concerned about the overall cost of this move and would like for us to: I am not going to block this effort - I can adjust my workflow accordingly and also see that a separate repo would benefit me too. Since the switch to monorepo, I expect all the essential components of LLVM to live inside llvm-project. I am concerned that a separate repository will actually make the Vim config less discoverable. Something that would contain ALL configs for ALL editors (e.g. ![]() Have you explored the possibility of cloning a subdirectory from various Vim plugin managers? Is a separate repo definitely the only option? I am thinking that perhaps we could try a separate LLVM sub-project first. I found GitHub - rhysd/vim-llvm: Vim filetype support for LLVM (including official files) while working on this proposal as an example, also as a point that this is useful and desirable.Ī separate repo can be used by all modern and modular vim plugin managers The initial transition should also be straightforward: taking the llvm-project/llvm/utils/vim directory out as-is makes it a usable vim plugin. As a vim plugin, it opens up opportunities for more vim integration that can be controlled by users, for example by vim global variables.A separate repo is easier to find, raising awareness and interest to update and improve the vim-integration.Installing could be as simple as adding one line, and updating as one vim command call. Installation flexibility: While you can still copy/link the files directly to use with vanilla vim, a separate repo can be used by all modern and modular vim plugin managers (vim-plug, vundle, packer for neovim, etc.).For example, the vimrc file is only provided as an inspiration, because we don’t have the modularity to turn specific settings on or off based on user preferences.Ī separate llvm-vim repo would make the vim util much easier to live on and work on: Limited functionalities: This also means our hands are tied when providing useful configurations.Hard to install/update (though admittedly probably not very frequent): As mentioned earlier, using the configurations now requires cloning the entire llvm-project repo, and involves manual steps every time they get updated.It’s not easy for new community members to find and use them, and more importantly to update and improve them. Low awareness: The configurations are buried deep in the monorepo.And copy-pasting selected parts from the inspirational vimrc file. To utilize these configurations, one must manually copy/link the directories and files to their vim config directory. A vimrc file that suggests coding style settings for working on the LLVM C++ codebase.Syntax highlighting, indentation, and some other default vim settings for those file types,.Llvm/utils/vim currently contains useful settings for people using vim-family editors to work on the LLVM project: I’m writing to propose moving the LLVM Vim configurations, currently at llvm-project/llvm/utils/vim/, out of the monorepo into its own repository.
0 Comments
Leave a Reply. |