aboutsummaryrefslogtreecommitdiff
path: root/vim
Commit message (Collapse)AuthorAgeFilesLines
* Update submodulesTom Ryder2018-06-012-0/+0
|
* Update submodules with Vim lint fixesTom Ryder2018-05-312-0/+0
|
* Correct comment typoTom Ryder2018-05-311-1/+1
|
* Merge auto_*dir.vim plugins into one, spun outTom Ryder2018-05-3110-263/+6
| | | | Functionality merged into new plugin auto_cache_dir.vim.
* Spin off command_typos Vim pluginTom Ryder2018-05-313-73/+0
| | | | Renamed as uncap_ex.vim.
* Spin off big_file_options Vim pluginTom Ryder2018-05-313-94/+0
|
* Update Vim pluginsTom Ryder2018-05-314-0/+0
|
* Spin off strip_trailing_whitespace Vim pluginTom Ryder2018-05-313-121/+0
|
* Spin off mail_mutt Vim pluginTom Ryder2018-05-313-122/+0
|
* Spin off copy_linebreak Vim pluginTom Ryder2018-05-313-124/+0
|
* Junk detect_background.vim and thereby autoloadTom Ryder2018-05-313-84/+5
| | | | | | | | | | | 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.
* Spin off toggle_option_flag Vim pluginTom Ryder2018-05-303-141/+0
|
* Spin off fixed_join Vim pluginTom Ryder2018-05-303-97/+0
|
* Spin off insert_suspend_hlsearch Vim pluginTom Ryder2018-05-303-76/+0
|
* Add feat requirements to hlsearch suspend docTom Ryder2018-05-301-2/+3
|
* Tidy comments, func names for 'hlsearch' suspendTom Ryder2018-05-301-9/+10
|
* Require +extra_search feat for 'hlsearch' suspendTom Ryder2018-05-301-1/+1
|
* Remove untidy commentTom Ryder2018-05-301-1/+0
|
* Merge branch 'hotfix/v0.34.1' into developTom Ryder2018-05-301-1/+0
|\ | | | | | | | | | | * hotfix/v0.34.1: Bump VERSION Remove stray echo from Vim plugin
| * Remove stray echo from Vim pluginTom Ryder2018-05-301-1/+0
| | | | | | | | | | This was probably left in during debugging. Because 'showmode' hides it, it didn't get noticed.
* | Use _save suffix for option caching variableTom Ryder2018-05-281-2/+2
|/ | | | | This makes it explicit what the variable is for, in the same way as s:cpoptions_save in vim/vimrc.
* Use script variable to keep showbreak settingTom Ryder2018-05-281-2/+3
| | | | | | | | | | | | The 'showbreak' option is global and has no local value--that is, it's not global-local--so `setlocal` actually just changes the global value, and hence we can't "change back" using `setlocal showbreak<`. Instead, keep the "normal" value in a script variable so that we can reliably switch back to it. This surprised me, as I had thought it was working, but I can't find even an older Vim that behaves the way I expected it too. I suppose I must just not have changed back often enough to actually notice.
* Update Vim plugin submodulesTom Ryder2018-05-252-0/+0
| | | | | * commentary * unimpaired
* Toggle Vim 'list', 'number' and 'wrap' globallyTom Ryder2018-05-182-3/+3
| | | | | | 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.
* Rebind Space in Vim normal mode to scrollTom Ryder2018-04-021-0/+3
| | | | I never use its normal function.
* Turn off Vim 'softtabstop' for CSV and TSV filesTom Ryder2018-02-172-2/+4
| | | | | Otherwise entering a Tab in insert mode inserts four spaces. I'm not sure how I didn't notice this before.
* Remove 'smarttab' settingTom Ryder2018-02-171-4/+0
| | | | | 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.
* Check for 'esckeys' option for NeoVimTom Ryder2018-02-161-1/+3
| | | | | NeoVim v0.2.3-708-g77286915a no longer includes this option, and raises an error if I try to set it.
* Update Vim plugin submodulesTom Ryder2018-02-122-0/+0
|
* Replace ftplugin/php.vim with custom versionTom Ryder2018-02-011-0/+38
| | | | | | | 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.
* Adjust explanation of PHP indent skipTom Ryder2018-02-011-3/+9
| | | | Include the variable guard, just for completeness' sake.
* Remove help ftdetect rulesTom Ryder2018-01-261-4/+0
| | | | No longer applicable since pathogen.vim was removed in 3e2740f.
* Remove vim-lion plugin for nowTom Ryder2018-01-261-0/+0
| | | | | | | | | | | | | | | 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.
* Actually remove pathogen bundle dirTom Ryder2018-01-231-0/+0
|
* Remove Pathogen from Vim setupTom Ryder2018-01-232-21/+6
| | | | | | | 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.
* Suspend 'C' from 'cpoptions' for sh syn extensionsTom Ryder2018-01-211-0/+12
| | | | This allows me to use line-breaking to keep the file readable.
* Join short-circuit line in detect_background.vimTom Ryder2018-01-211-2/+1
| | | | | This makes the block work correctly when 'compatible' is set and 'C' is in 'cpoptions'.
* Break some continued lines in Vim indent filesTom Ryder2018-01-213-6/+4
| | | | | This will mean they load correctly when the 'C' flag preventing line-breaking is in 'cpoptions', and 'compatible' is set.
* Remove 'mac' from 'fileformats'Tom Ryder2018-01-211-4/+0
| | | | | | | | 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.
* Tweak 'cpoptions' C flag instead of 'nocompatible'Tom Ryder2018-01-211-2/+14
| | | | | | | | | | | | | | | | | | | | | 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.
* Remove a baseless assertion I made in a configTom Ryder2018-01-201-2/+1
| | | | | Don't claim that syntax files tend to assume 'autoindent' is set, as it doesn't seem to be true.
* Make entire syntax config dependent on load stateTom Ryder2018-01-201-5/+3
|
* Activate syntax settings conditionallyTom Ryder2018-01-201-2/+4
| | | | | | | | | 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.
* Refactor directory creation in pluginsTom Ryder2018-01-173-12/+12
| | | | No functional changes here, just removing a little duplicate code.
* Remove HTML and PHP syntax highlighting tweaksTom Ryder2018-01-172-5/+0
| | | | | The things they were intended to fix aren't actually that bad, on review.
* Clear unwanted syntax group, don't link to NONETom Ryder2018-01-171-1/+1
|
* Correct monospaced blocks in Vim plugin docsTom Ryder2018-01-083-4/+4
| | | | Close unclosed blocks, and remove an unwanted block.
* Add syntax checking with zsh -n for Z shellTom Ryder2017-11-232-0/+66
|
* Merge branch 'hotfix/v0.19.1' into developTom Ryder2017-11-231-0/+3
|\ | | | | | | | | | | * hotfix/v0.19.1: Bump VERSION Restore 'nocompatible' set to vimrc
| * Restore 'nocompatible' set to vimrcTom Ryder2017-11-231-0/+3
| | | | | | | | | | | | Otherwise, the line-continuation in the ~/.vimrc fails if compatibility mode survives the invocation step, for example if the vimrc file is sourced directly with the -u option, or if vim is invoked as "ex".