Since this is Vim Script code, I wrapped it with the vim.cmd() function to get the following: vim.cmd([[ \ 'ib' :1, " Support nesting of parentheses \ 'i]' :1, " Support nesting of square brackets (NOTE: Remove comments in dictionary before sourcing) Per the vim-expand-region documentation, I should expand the “text objects the plugin knows about with g:expand_region_text_objects”, e.g.: " Default settings. In my a file I am no longer trying to source anything. I now have require "user.vim-expand-region" in my a file. I thought that the plugin wasn’t working because repeated typing of “+” isn’t expanding the highlighted section. First “*.vim” are sourced, then “*.lua” files.” In the help (:h load-plugins) it states “all directories in ‘runtimepath’ will be searched for the “plugin” sub-directory and all files ending in “.vim” or “.lua” will be sourced (in alphabetical order per directory), also in subdirectories. In Vim, it seems like many people use the Plug package manager, but I’m not sure if it’s a good idea to mix multiple package managers (Packer + Plug) in one config.Īnyway, I’m clearly a little confused and would be grateful for any tips. git: which is pretty common for a package manager. For Vim, it seems like the plugin should be added to ~/.vim/pack/bundle/start but that’s not where it gets installed with Packer. According to the README, the plugin has the following dependencies: Vim >7.4 or neovim: while keeping Vim up to date is a good thing, it may be problematic for some users that previous versions are not supported. I tried installing vim-expand-region with Packer, which resulted in this structure: ~/.local/share/nvim/site/pack/packer/start/vim-expand-region/įrom some of the instructions listed here it seems like the expand_region.vim file needs to be sourced. ~/.local/share/nvim/site/pack/*/start/plugin/lua/a) which I assume gets sourced when the require function is called. In my case, my runtime path includes ~/.local/share/nvim/site/pack/*/start/* and each of the lua plugins installed with Packer contains a lua directory with a a file (e.g. Vim.notify("WARNING: a failed to load.")Īs I understand it, the require function searches the runtime path looking for a file called “a” to load.
#VIM PLUGINS CODE#
Then, in the a file, I require the plugin itself with code like: local status_ok, plugin = pcall(require, "plugin") lua plugin, I run require "ugin" in my a file. My current config is organized like this: ~/.config/nvim/Īs described in the nanotee guide, to load a.
#VIM PLUGINS INSTALL#
Up till now, I’ve only ever used plugins written in Lua in Nvim and installed them using Packer, but now I’m trying to install a few Vim plugins like vim-expand-region and vindent which are written in Vim Script.
#VIM PLUGINS HOW TO#
Here's what I got.Can anyone provide some guidance on how to load Vim (Vim Script) plugins in Neovim? Now you probably want more Vim plugins because it's never enough. If you know more interesting plugins, please don't hesitate to share. Limelight dims non-active paragraphs of the file, thus letting you focus on the current one. Junegunn Choi is a prolific author of several super-hit plugins like FZF and vim-plug. I'm using it to overview and navigate the code quickly. LSP clients nowadays can build a tree of your program (symbol tree?) similar to some full-blown IDEs. This plugin puts the cursor at the place it was the last time you edited the file. Long story short, it shrinks all the other splits beside the current one. You might find this one handy if you're a heavy splits users ( everyone loves splits!).
Unfortunately, it seems to be unmaintained, but here's a maintained fork. I switched to it from gruvbox and am happy so far. This one is a color scheme and a pretty convincing one (the top screenshot in this article). Honestly, I'm not using it all that much, as I still get kicks out of my FZF. It uses modern popup APIs (supports both Vim 8+ and Neovim). Vim-clap allows you to fuzzy-find anything from files to Git commits.
Instead of reaching to Google, I can do it from the cozy comfort of my Vim. While I understand that might be a super popular use-case, I need to look up a word definition or a synonym, especially when writing articles or code comments. Remember Tim Pope's surround.vim plugin that allows you to wrap and re-wrap chunks of text with brackets, quotes, etc.? This one is very similar but it also highlights the wrapping text, making it much more convenient. You know that feeling when you yanked some text but not quite sure if you pressed the right key combination? This plugin shortly highlights whatever you just yanked.
Or you can copy-paste it and use your favorite plugin manager.
0 kommentar(er)
