| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
Looks like these were getting categorised as "rc", or "M$ Resource
files", in the core filetype.vim.
|
|
|
|
| |
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.
|
|
|
|
|
| |
Keeping the tests at the beginning of plugins on one line without
continuations is needed to work around &cpo-=C.
|
|
|
|
| |
They don't have local analogues; they're global options.
|
|
|
|
|
| |
There is no such setting as "longest:list". What I meant was
"list:longest".
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The DESCRIPTION heading for each of these is filled out now, but some of
them probably need a bit more explanation. The mail_mutt.txt plugin is
good, though.
|
| |
|
|
|
|
|
| |
This matches .txt files in any 'doc' directory with 'vim' or '.vim' in
its ancestry.
|
| |
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
This variable is not set in older Vims (early 6.x), and I think it's
worth guarding for.
|
|
|
|
|
|
| |
This error seems to be raised when ShellCheck can't source a file
because its filename is not known until runtime. I don't want it to do
that anyway, so I've just excluded it by default.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a relatively drastic change that should have been done
progressively, but I got carried away in ripping everything out and
putting it back in again.
Reading the documentation for writing a Vim script (:help usr_41.txt), I
am convinced that all of the content that was in the vim/ftplugin
directory and some of the vim/indent directory actually belonged in
vim/after/ftplugin and vim/after/indent respectively.
This is because the section on filetypes makes the distinction between
replacing the core filetype or indent plugins and merely adding to or
editing them after the fact; from :help ftplugin:
> If you do want to use the default plugin, but overrule one of the
> settings, you can write the different setting in a script:
>
> setlocal textwidth=70
>
> Now write this in the "after" directory, so that it gets sourced after
> the distributed "vim.vim" ftplugin after-directory. For Unix this
> would be "~/.vim/after/ftplugin/vim.vim". Note that the default
> plugin will have set "b:did_ftplugin", but it is ignored here.
Therefore, I have deleted the user_indent.vim and user_ftplugin.vim
plugins and their documentation that I wrote, and their ftplugin.vim and
indent.vim shims in ~/.vim, in an attempt to make these plugins
elegantly undo-ready, and instead embraced the way the documentation and
$VIMRUNTIME structure seems to suggest.
I broke the ftplugin files up by function and put them under
subdirectories of vim/after named by filetype, as the 'runtimepath'
layout permits. In doing so, I also carefully applied the
documentation's advice:
* Short-circuiting repeated loads
* Checking for existing mappings using the <Plug> prefix approach
* Avoiding repeated function declarations overwriting each other
* Guarding against 'cpotions' mangling things (by simply
short-circuiting if 'compatible' is set).
I've made the b:undo_ftplugin and b:undo_indent commands less forgiving,
and append commands to it inline with the initial establishment of the
setup they're reversing, including checking that the b:undo_* variable
actually exists in the first place.
For the indentation scripts, however, three of the four files originally
in vim/indent actually do belong there:
1. csv.vim, because it doesn't have an indent file in the core.
2. tsv.vim, because it doesn't have an indent file in the core.
3. php.vim, because it does what ftplugins are allowed to do in
preventing the core indent rules from running at all.
The indent/vim.vim rules, however, have been moved to
after/indent/vim.vim, because the tweaks it makes for two-space
indentation are designed to supplement the core indent rules, not
replace them.
Finally, I've adjusted Makefile targets accordingly for the above, given
the vim/ftplugin directory is now empty and there are three new
directories in vim/after to install. We wrap these under a single
`install-vim-after` parent target for convenience. The
`install-vim-after-ftplugin` target accommodates the additional level of
filetype directories beneath it.
|
|
|
|
| |
user_ftplugin.vim and user_indent.vim seem to be missing it.
|
|\
| |
| |
| |
| |
| |
| | |
* 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.
|
| | |
|