sheerun / vimrc

Basic vim configuration for your .vimrc

vimrc.vim

This plugin replaces lion's share of your .vimrc. A superset of vim-sensible.

Installation

Just include with some package manager. For example if you use vim-plug, then write:

Plug 'sheerun/vimrc'

I recommend to use:

• Set your leader to space
• vim-plug as lightweight plugin manager
• vim-polyglot for syntax highlighting

An example of simple .vimrc file:

" Select your Leader key
let mapleader = "\<Space>"

call plug#begin()

Plug 'sheerun/vimrc'
Plug 'sheerun/vim-polyglot'

call plug#end()

Features

Every set default setting is documented in the source. You can read it here and here

License

The same terms as Vim itself. See :help license.

vimrc's Issues

Neovim: E518: Unknown option: cursorlineopt=number

Trying Neovim with this minimal init.vim

let mapleader = "\<Space>"

:filetype plugin on
:syntax on
:filetype indent on

call plug#begin('~/.config/nvim/plugged')

Plug 'sheerun/vimrc'
Plug 'sheerun/vim-polyglot'
Plug 'phanviet/vim-monokai-pro'

call plug#end()

colorscheme monokai_pro

After installing and reloading I get the error:

Error detected while processing /home/cameron/.config/nvim/plugged/vimrc/plugin/vimrc.vim:
line  179:
E518: Unknown option: cursorlineopt=number

I commented out the offending line in the plugged/vimrc/plugin/vimrc.vim file and the error went away.

Turning mouse off

I like the settings except for one, set mouse=a. Is there a way to have the plugin not set this?

Visual bell gets enabled through this plugin

For some reason that is way beyond my understanding, this plugin tries to disable bells but enables visual bells instead.
After downloading this repo via vim-plug, I consistently get visual bells after an "illegal" action.
Once I comment it out, the bells are gone again.
The most likely cause of that is https://github.com/sheerun/vimrc/blob/master/plugin/vimrc.vim#L213.
As this repo is also used inside vim-polyglot, this issue extends there unless

let g:polyglot_disabled = ['sensible']

is called explicitly.
I found a solution to this problem, namely adding

set belloff=all

as line 214.
EDIT: This feature seems to have been accepted to vim in patch 7.4.793, which was made in July 2015. Is it safe to assume that this version is used in clients, or should this call be wrapped in a has query?

I hate the visual bells as they disturb you even more than a normal bell (at least there you can turn off your sound, but try that with a visual feature…), so I hope that that is not an intentional feature.
The comment

" Disable any annoying beeps on errors.

would appear to me as this being accidental.

An alternative, if this was not accidental, would be to offer a configuration option that simply turns visual bells on or off.
Another alternative would be to drop the call creating visual bells and let users add it themselves as I am pretty sure most users do not want visual bells → opt-in.
A fourth alternative is to let users individually call the solution mentioned above → opt-out.

I definitely prefer the opt-in mechanism the most as whoever wants visual bells, can still enable them themselves and whoever doesn't want it does not have to opt-out.

signcolumn=no have problems with vim-gitgutter

The plugin vim-gitgutter (https://github.com/airblade/vim-gitgutter) use the signcolumn to show differences with vim original file (differences, deleted and added lines)

vimrc disables fully signcolumn with neovim 0.4.3 (i imagine for a vim 8.x backport) and i need to enable manually signcolumn to see the differences.

maybe one setting to don't disable signcolumn can be of help or ... integrate plugin with vim-gitgutter ...