| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| | |
* release/v0.28.0:
Bump VERSION
Update Vim plugin submodules
Add missing options terminator to Makefile
Suppress error messages in td(1df)
|
| | |
|
| |\
| | |
| | |
| | |
| | | |
* release/v0.27.0:
Bump version to 0.27.0
|
| |\ \
| | | |
| | | |
| | | |
| | | | |
* feature/vim-submods:
Update Vim plugin submodules
|
| |/ / |
|
| |\ \
| | | |
| | | |
| | | |
| | | | |
* feature/makefile:
Add missing options terminator to Makefile
|
| |/ / |
|
| |\ \
| | | |
| | | |
| | | |
| | | | |
* feature/td-quiet:
Suppress error messages in td(1df)
|
| |/ /
| | |
| | |
| | |
| | | |
Don't report to the user when a repository is created, and ignore errors
from git-diff-index(1) for when there is no HEAD
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
* release/v0.27.0:
Bump version to 0.27.0
Replace ftplugin/php.vim with custom version
Adjust explanation of PHP indent skip
Remove help ftdetect rules
|
| |/ |
|
| |\
| | |
| | |
| | |
| | |
| | | |
* feature/vim-php:
Replace ftplugin/php.vim with custom version
Adjust explanation of PHP indent skip
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Per the comment in the new file, this is to avoid loading in HTML
ftplugins as well, a curiosity of the stock ftplugin/php.vim file that's
probably a well-intentioned way of accommodating templated files with a
mix of PHP and HTML in them.
|
| |/
| |
| |
| | |
Include the variable guard, just for completeness' sake.
|
| |\
| | |
| | |
| | |
| | | |
* feature/vim-ftdetect:
Remove help ftdetect rules
|
| |/
| |
| |
| | |
No longer applicable since pathogen.vim was removed in 3e2740f.
|
| |\
| | |
| | |
| | |
| | |
| | | |
* hotfix/v0.26.3:
Bump version number to 0.26.3
Remove vim-lion plugin for now
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | | |
* hotfix/v0.26.2:
Bump version number to 0.26.2
Actually remove pathogen bundle dir
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* hotfix/v0.26.1:
Bump version number to 0.26.1 (hotfix)
Exclude root-level files from Vim bundles
Restore install-vim-autoload target
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* release/v0.26.0:
Bump version number to 0.26.0
|
|\ \ \ \ \ \
| | |_|_|_|/
| |/| | | |
| | | | | |
| | | | | |
| | | | | | |
* hotfix/v0.26.3:
Bump version number to 0.26.3
Remove vim-lion plugin for now
|
| | | | | | |
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It doesn't have guards for old Vim, compatibility settings, or
repeat-reload checks, which is not very good, and means it spits errors
on old Vims about newer constructs like :finally, where all the other
plugins are well-behaved.
I was going to replace it with vim-easy-align, but that doesn't seem to
have a version or compatibility guard either, though it does have a
repeat-reload check which means I could probably shoehorn in a version
check before loading it, but even that seems a bit gross.
So, I might just leave lining things up nicely to the various tidy
scripts. Let's see how much I miss it.
|
|\ \ \ \ \
| | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | | |
* hotfix/v0.26.2:
Bump version number to 0.26.2
Actually remove pathogen bundle dir
|
| | | | | |
|
|/ / / / |
|
|\ \ \ \
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | | |
* hotfix/v0.26.1:
Bump version number to 0.26.1 (hotfix)
Exclude root-level files from Vim bundles
Restore install-vim-autoload target
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Create the plugin directory hierarchy first, and then copy the files in
as long as they're at least one file deep. This prevents files like
README.markdown landing in ~/.vim.
|
|/ / /
| | |
| | |
| | | |
It was mistakenly removed in 3e2740f for v0.26.0.
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | | |
* release/v0.26.0:
Bump version number to 0.26.0
Remove Pathogen from Vim setup
|
| |/ |
|
| |\
| | |
| | |
| | |
| | | |
* feature/no-pathogen:
Remove Pathogen from Vim setup
|
| |/
| |
| |
| |
| |
| |
| | |
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.
|
| |\
| | |
| | |
| | |
| | | |
* release/v0.25.0:
Bump version number to 0.25.0
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* release/v0.25.0:
Bump version number to 0.25.0
Suspend 'C' from 'cpoptions' for sh syn extensions
Join short-circuit line in detect_background.vim
Break some continued lines in Vim indent files
Remove 'mac' from 'fileformats'
Tweak 'cpoptions' C flag instead of 'nocompatible'
Remove a baseless assertion I made in a config
Make entire syntax config dependent on load state
Activate syntax settings conditionally
|
| |/ |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* feature/vimrc-review:
Suspend 'C' from 'cpoptions' for sh syn extensions
Join short-circuit line in detect_background.vim
Break some continued lines in Vim indent files
Remove 'mac' from 'fileformats'
Tweak 'cpoptions' C flag instead of 'nocompatible'
Remove a baseless assertion I made in a config
Make entire syntax config dependent on load state
Activate syntax settings conditionally
|
| | |
| | |
| | |
| | | |
This allows me to use line-breaking to keep the file readable.
|
| | |
| | |
| | |
| | |
| | | |
This makes the block work correctly when 'compatible' is set and 'C' is
in 'cpoptions'.
|
| | |
| | |
| | |
| | |
| | | |
This will mean they load correctly when the 'C' flag preventing
line-breaking is in 'cpoptions', and 'compatible' is set.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In order for the configuration to be successfully loaded, the only
option in the vi 'cpoptions' settings for 'compatible' is "C". From
:help 'cpoptions':
> C Do not concatenate sourced lines that start with a backslash.
> See line-continuation.
With this flag removed from 'cpoptions' if 'compatible' does happen to
be set, the configuration parses just fine, and then we can put it back
at the end if we need to.
This is a less aggressive approach than just turning off 'compatible'
entirely if it happens to be set, whether because the user wanted it
that way before loading the configuration or because Vim was started as
ex(1).
My plugins and ftplugins are all conditional on 'compatible' not being
set, anyway.
|
| | |
| | |
| | |
| | |
| | | |
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.
|
| |\
| | |
| | |
| | |
| | | |
* release/v0.24.0:
Bump version number to 0.24.0
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | | |
* release/v0.24.0:
Bump version number to 0.24.0
Always add --log to `git merge`
Refactor directory creation in plugins
Remove HTML and PHP syntax highlighting tweaks
Clear unwanted syntax group, don't link to NONE
|
| |/ |
|
| |\
| | |
| | |
| | |
| | | |
* feature/vim-plugin:
Refactor directory creation in plugins
|