| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
And add .vim/script.vim, to be composed in the next commit
|
| | |
|
| |
|
|
|
|
| |
Intelligently choose how to load matchit.vim, and clean up the
short-circuit variables for the unwanted distribution plugins in an
"after" plugin script.
|
| | |
|
| |
|
|
|
|
| |
Replace it with new plugin put_blank_lines.vim and new mappings to cycle
between open buffers: the only features from the plugin that I actually
use in recent memory.
|
| | |
|
| |
|
|
| |
Functionality merged into new plugin auto_cache_dir.vim.
|
| |
|
|
|
|
|
|
|
|
|
| |
It's too complicated and confusing, and doesn't do enough to justify
wrecking Vim's own logic for doing this sort of thing. Better to just
say `:set background=dark` and be done with it.
This is the only one of my inline plugins with an `autoload` file, so we
can get rid of that, too.
Not worth packaging/publishing to www.vim.org.
|
| |
|
|
|
|
| |
No particular reason beyond preference; I think of these as properties
of the window itself, not the window-buffer pair, so it makes more sense
to me this way.
|
| |
|
|
| |
I never use its normal function.
|
| |
|
|
|
| |
In practice, I don't actually use this; I do ^V^I, and I seldom need
literal tabs anyway. Better to leave the behaviour predictable.
|
| |
|
|
|
| |
NeoVim v0.2.3-708-g77286915a no longer includes this option, and raises
an error if I try to set it.
|
| |
|
|
|
|
|
| |
Given that all of this is installed rather than symbolically linked,
there's not really any harm following the old mixed ~/.vim layout for
plugins. It's one less dependency and it makes the setup quite a bit
less complicated.
|
| |
|
|
|
|
|
|
| |
It seems unlikely that I'll ever edit a MacOS encoded file in my
lifetime on the Unix and Windows systems to which these dotfiles are
deployed, and when 'compatible' is set, the default empty value for this
option breaks everything with a bunch of ^J characters in every
god-fearing file. Not worth the trouble.
|
| |
|
|
|
| |
Don't claim that syntax files tend to assume 'autoindent' is set, as it
doesn't seem to be true.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Per an oft-made recommendation on /r/vim .vimrc review threads:
<https://www.reddit.com/r/vim/comments/6znskl/vimrc_review_thread/dnbmvxv/>
> Re-sourcing the vimrc won't clobber any of your personal highlight
> settings and the if part helps avoid unneeded re-execution/reprocessing.
|
| |
|
|
|
| |
This seems to be necessary for a location-list-based :lmake system to
work for checking and linting. I'll figure out exactly why a bit later.
|
| |
|
|
|
|
|
|
|
|
| |
From :help mapleader:
> Note that the value of "mapleader" is used at the moment the mapping
> is defined. Changing "mapleader" after that has no effect for already
> defined mappings.
So the order of evaluation matters.
|
| | |
|
| |
|
|
| |
Most of them, anyway. A couple of them are sane and useful.
|
| | |
|
| |
|
|
|
|
| |
It's easily repackaged and it makes the configuration that much shorter,
so I may as well. This version also correctly handles 'hlsearch' not
being on in the first place.
|
| |
|
|
| |
They don't have local analogues; they're global options.
|
| |
|
|
|
| |
There is no such setting as "longest:list". What I meant was
"list:longest".
|
| | |
|
| |
|
|
|
|
|
| |
If there are no mappings to the <Plug>FixedJoin target that the
fixed_join.vim plugin provides at the time it is loaded, and the
line-joining function of normal-mode J is not already mapped, the plugin
will try to map it itself, for a more plug-and-play.
|
| |\
| |
| |
| |
| |
| |
| | |
* feature/vim-mutt-plug:
Move mutt_mail.vim line select logic into plugin
Add new mail_mutt.vim plugin, apply mappings
Beginnings of a buffer-to-Mutt mailer plugin
|
| | |
| |
| |
| | |
This makes the configuration shorter and easier to read.
|
| | |
| |
| |
| |
| | |
This plugin provides a shortcut for staring email messages in Mutt with
a range of lines.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
These flags prevent multiple messages from reading or writing multiple
files from queuing up and forcing an enter prompt. They're part of the
default, which is why I didn't notice their absence until I tried using
the setting previous to this commit and opened two files at once.
|
| | |
| |
| |
| |
| | |
Most of these are actually the default; may as well explicitly set and
document them, however. t and T in particular are new.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
From :help hidden-options:
>Not all options are supported in all versions. This depends on the
>supported features and sometimes on the system. A remark about this is
>in curly braces below. When an option is not supported it may still be
>set without getting an error, this is called a hidden option. You can't
>get the value of a hidden option though, it is not stored.
>
>To test if option "foo" can be used with ":set" use something like this:
> if exists('&foo')
>This also returns true for a hidden option. To test if option "foo" is
>really supported use something like this:
> if exists('+foo')
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
For plugin-specific configuration.
|
| | |
| |
| |
| |
| | |
This will allow the Windows-specific stuff in my new auto_* plugins to
quote filenames correctly.
|
| | |
| |
| |
| | |
For OS-dependent config.
|
| | |
| |
| |
| | |
I never use it. May as well defer to the vi default.
|
| | | |
|
| | |
| |
| |
| | |
'paste' is specific to the terminal only anyway.
|
| | | |
|
| | |
| |
| |
| | |
Clearer filename and more consistent to use the noun.
|
| | |
| |
| |
| | |
A little clearer and a needless abbreviation anyway.
|
| | |
| |
| |
| | |
More likely to share options this way.
|
