Hot answers tagged

3

Use vim-commentary plugin, it has buffer-local variable b:commentary_startofline you can setup per filetype: let b:commentary_startofline = 1 See patch https://github.com/tpope/vim-commentary/commit/62b68aecec2de531bc3978bfb9c07d3b6759ce0e


2

If you're running that code block from inside a vimrc file (or init.vim for NeoVim), that will explain why the :Fern command will not be available yet, since the code in a vimrc will run before plug-in initialization code is executed and custom plug-in commands are only defined there. In order to have the call only happen once plug-ins have initialized (at ...


1

Knowing from :help ale-python-pylint that we want to adjust g:ale_python_pylint_options to include --rcfile, I would drop let g:ale_python_pylint_options = '--rcfile '.<filename> in wherever the right place is for you. That could be wherever you configure ALE, if a single setting is right; or, it could be in an ftplugin (use b:…) if you need to change ...


1

You might like UltiSnips. It's a bit complex (but you could say most snippet plug-ins are), but you can find screen casts covering UltiSnips to help you get started with it. You'll probably want to use the snippets from honza/vim-snippets together with UltiSnips (in fact, the UltiSnips quick start instructions mention them specifically.) They should cover a ...


1

In mu-template case, that I'm maintaining, you'll have to register at least 4 plugins in your plugin manager -- yeah, I know, 4 seems a lot, but I don't like duplicating my code, and I'm dreaming of a day when people will use plugin managers that handle dependencies... The main, required, plugins: 'LucHermitte/lh-vim-lib' 'LucHermitte/lh-style' 'LucHermitte/...


Only top voted, non community-wiki answers of a minimum length are eligible