| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Interestingly, the :compiler for the "php" filetype doesn't include the
% or %:S bit in the `makeprg`, but that's easily worked around by moving
that logic into the check script itself.
|
| |
|
| |
|
|
|
|
| |
This seems to be necessary for Vim 6.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
I didn't know about :compiler until now. From :help
write-compiler-plugin:
> A compiler plugin sets options for use with a specific compiler. The
> user can load it with the |:compiler| command. The main use is to set
> the 'errorformat' and 'makeprg' options.
Vim even has "perl" and "tidy" compilers already that seem to work
really well. I'll just add in my own and install them.
|
|
|
|
|
|
| |
The checker is a bit dicey; I hope that format is reliable. It may turn
out to be better to depend on Vi::QuickFix or a similar module. We'll
see.
|
|
|
|
|
| |
This opens the error list in the location list for the error list if
there were any. It seems to work well.
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|\
| |
| |
| |
| | |
* feature/vim-sh:
Coax sh.vim into accepting #/% param expansion
|
| |
| |
| |
| | |
These forms of parameter expansion are specified in POSIX sh.
|
|/
|
|
|
| |
I missed the filetype prefix I had added to the function call in the
actual declaration of the function itself.
|
|
|
|
|
|
|
|
| |
This was causing the following error on load:
> Error detected while processing /home/tom/.vim/plugin/auto_undodir.vim:
> line 48:
> E580: :endif without :if: endif
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| |
| |
| | |
* feature/vim-plug:
Check for shellescape() function before using it
|
| |
| |
| |
| | |
It was added in patch 111 for Vim 7.0.
|
|/ |
|
|
|
|
|
| |
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
|