|Number of watchers on Github||2906|
|Number of open issues||20|
|Average time to close an issue||about 2 months|
|Average time to merge a PR||3 days|
|Open pull requests||5+|
|Closed pull requests||35+|
|Last commit||over 2 years ago|
|Repo Created||over 7 years ago|
|Repo Last Updated||over 2 years ago|
|Organization / Author||tpope|
|Do you use vim-sensible? Leave a review!|
|View open issues (20)|
|View vim-sensible activity|
|View on github|
|Fresh, new opensource launches 🚀🚀🚀|
Software engineers: It's time to get promoted. Starting NOW! Subscribe to my mailing list and I will equip you with tools, tips and actionable advice to grow in your career.
Think of sensible.vim as one step above
'nocompatible' mode: a universal
set of defaults that (hopefully) everyone can agree on.
scpthis up to make things a bit more tolerable.
If you don't have a preferred installation method, I recommend installing pathogen.vim, and then simply copy and paste:
cd ~/.vim/bundle git clone git://github.com/tpope/vim-sensible.git
See the source for the authoritative list of features. (Don't worry, it's
:set calls.) Here's a taste:
'backspace': Backspace through anything in insert mode.
'incsearch': Start searching before pressing enter.
:set list(visible whitespace) prettier.
'scrolloff': Always show at least one line above/below the cursor.
'autoread': Autoload file changes. You can undo by pressing
runtime! macros/matchit.vim: Load the version of matchit.vim that ships with Vim.
How can I see what this plugin actually does?
The source is authoritative. Use
:help 'option' to see the
documentation for an option. If you install scriptease.vim, you can press
K on an option (or command, or function) to jump to its documentation.
How can I override a setting?
Normally, sensible.vim loads after your vimrc, making it a bit tricky to
override (although you could use
after/plugin/sensible.vim). If you want to
load it earlier, add the following line to you vimrc, then put your overrides
Feel free to let me know which setting you object to, so I can reassess whether it makes sense to include it.
I want this to be a plugin nobody objects to installing. Let me know if you have any objections to anything. There are a handful of settings I figured might be controversial, but I included anyways, just to settle the question once and for all. It won't take much persuasion for me to remove them. Everything else is negotiable.
Feel free to ask a question if you're not sure why I've set something, as I haven't put much effort into documenting that.
I'm a stickler for commit messages, so if you send me a pull request with so much as a superfluous period in the subject line, I will close it without so much as a second thought, and save my precious attention for someone who can actually follow directions.
This pairs great with sleuth.vim.
Copyright Tim Pope. Distributed under the same terms as Vim itself.