| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
This is the natural way of things, I think.
|
|
|
|
|
|
| |
I love the way this works when writing mail, and find myself missing it
when writing Git commits that include block quotes. This is ported from
ftplugin/mail.vim.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Should have done some of this in separate commits; oh well.
* Rewrite headers for each ftplugin
* Require Vim version >= 7.0, and thereby:
* Switch back to location list
* Don't check for b:undo_ftplugin existence, assume it
* Save and restore compiler instead of internal options
* Add bash, ksh, sh, and shellcheck compilers
* Rename mail/format_flowed.vim to mail/flowed.vim
* Rename sh/bash_han.vim to sh/han.vim
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This reverts commit a14bc50. Changed my mind; decided it's tidier this
way.
|
|
|
|
|
|
|
| |
Because we use our own private copies of the primary filetype plugins,
they'll get loaded in the correct order from here.
Also adjust Makefile to accommodate the extra level.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
No advantage to making them autoload
|
|
|
|
|
|
| |
The stock markdown.vim file loads in all the html.vim ftplugins too.
This is probably a good idea for the stock files, but none of my HTML
extension plugins are appropriate for Markdown, so exclude them.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
* Add a function to suspend autoformatting for the duration of pasting
lines.
* Factor the ftplugin's functions out to be autoloaded; this requires
Vim >=7.0, but it already needed that.
* Add Makefile infrastructure for new autoload directories/files.
|
| |
|
| |
|
|
|
|
|
|
| |
Intelligently choose how to load matchit.vim, and clean up the
short-circuit variables for the unwanted distribution plugins in an
"after" plugin script.
|
|
|
|
| |
This allows me to use line-breaking to keep the file readable.
|
|
|
|
|
| |
This will mean they load correctly when the 'C' flag preventing
line-breaking is in 'cpoptions', and 'compatible' is set.
|
|
|
|
|
| |
The things they were intended to fix aren't actually that bad, on
review.
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|\
| |
| |
| |
| | |
* 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 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.
|
|
|
|
|
|
| |
The syntax highlighter flags this code with an error on the final square
bracket: `case $foo in [![:ascii:]]) ;; esac`, but that's all legal. I'm
not yet sure how to fix it, so will just turn the error group for now.
|
|
|
|
|
|
|
| |
These two changes coax syntax/sh.vim into realising that POSIX shell
does not specify 'until' as a builtin (that's a Bash/Ksh thing), and
that POSIX shell is able to nest 'while' loops within other blocks
(that's not a Bash/Ksh thing).
|
|
|
|
|
|
| |
This is what was missing after I initially redefined these groups and
stopped all POSIX shell scripts thinking they were POSIX. The words now
highlight correctly when within control structures again.
|
|
|
|
|
| |
It's not a shell builtin in `dash`, but it is in `Bash`, and I kind of
think of it that way.
|
| |
|