local_vimrc
lh-misc
| local_vimrc | lh-misc | |
|---|---|---|
| 5 | 3 | |
| 125 | 17 | |
| - | - | |
| 1.8 | 6.2 | |
| over 3 years ago | 17 days ago | |
| Vim Script | Vim Script | |
| GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
local_vimrc
-
How can I have a local .vimrc file that is used only inside a certain directory?
Other approaches are available as well. For instance, autocommands in the .vimrc are possible as well, but every time you move around that directory you'd have to update the autocommand.
-
What is the best config/setup/plugins for C development in Vim?
Regarding project management, .exrc is enough as long we're working on simple project where everything is in the same directory. On real project I've ended up needing and writing much, much more.
-
manual ctags with vim-gutentags or similar
buffer wise, from a local vimrc for instance, with let b:tag_options = { 'no_auto': 0}
-
search and replace camelCase to snake_case
snake is one of the possible naming policies. Several are hard-coded: snake, UpperCamelCase, lowerCamelCase, SCREAMING_SNAKE_CASE. Other can be configured (in local vimrc plugins for instance), and then used where we can expect it to make sense: member variables, local variables, static variables, types, getter...
-
A per project vimrc based on direnv
I'm not sure about the new plugin advertised, but 'exrc' is restricted to the current directory. Its settings won't be applied to subdirectories -- unlike to what other localvimrc plugins do
lh-misc
-
Setting a b: or g: variable in a modeline
the plugin file to drop in ~/.vim/plugin/: https://github.com/LucHermitte/lh-misc/blob/master/plugin/let-modeline.vim
-
Example of compile_flags.txt for windows
Note: as I often install clang on machines where I'm not root, I often have to feed these paths to the LSP server I use, or even to libclang. In the end, I automatically ask the pathnames after Vim has started (system() cannot be used directly in the vimrc), and feed them to ccls (through coc).
-
Coding in C++
First if your installation of clang+libc++ is non standard (/usr/(local/)), you'll have to register the path to the system includes (which can be automated).
What are some alternatives?
vimrc - The ultimate Vim configuration (vimrc)
Bear - Bear is a tool that generates a compilation database for clang tooling.
vim-abolish - abolish.vim: Work with several variants of a word at once
lh-vim-lib - Library of Vim functions
lh-tags - ctags base updating, and browsing from vim
coc-clangd - clangd extension for coc.nvim
cquery - C/C++ language server supporting multi-million line code base, powered by libclang. Emacs, Vim, VSCode, and others with language server protocol support. Cross references, completion, diagnostics, semantic highlighting and more
clangd - clangd language server
clang_complete - Vim plugin that use clang for completing C/C++ code.
nerdtree - A tree explorer plugin for vim. [Moved to: https://github.com/preservim/nerdtree]
ale - Check syntax in Vim/Neovim asynchronously and fix files, with Language Server Protocol (LSP) support
nerdtree - A tree explorer plugin for vim.