aboutsummaryrefslogtreecommitdiff
path: root/vim
Commit message (Collapse)AuthorAgeFilesLines
* 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".
* | Update sahara submoduleTom Ryder2017-11-231-0/+0
|/
* Add `php -l` check binding for PHP filetypeTom Ryder2017-11-201-0/+57
| | | | | | 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.
* Correct "fi" to "endif" in new compiler filesTom Ryder2017-11-202-2/+2
|
* Use %:S expansion only when availableTom Ryder2017-11-192-2/+14
|
* Force g:current_compiler removal before check/lintTom Ryder2017-11-196-2/+6
| | | | This seems to be necessary for Vim 6.
* Use quickfix window for check/lintTom Ryder2017-11-196-12/+12
|
* Use :compiler quickfix systems for Vim/HTML lintTom Ryder2017-11-192-2/+28
|
* Use :compiler scripts for makeprg setupTom Ryder2017-11-194-4/+24
| | | | | | | | | | | | 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.
* Add :lwindow support to Perl check/lintTom Ryder2017-11-192-2/+30
| | | | | | 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.
* Adapt sh check/lint to use :lmakeTom Ryder2017-11-192-10/+42
| | | | | This opens the error list in the location list for the error list if there were any. It seems to work well.
* Remove 'shellpipe' settingTom Ryder2017-11-191-3/+0
| | | | | 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.
* Use single-quotes for strings in sh.vimTom Ryder2017-11-151-1/+1
|
* Use full word "syntax" in sh.vimTom Ryder2017-11-151-3/+3
|
* Merge branch 'feature/vim-sh' into developTom Ryder2017-11-151-0/+15
|\ | | | | | | | | * feature/vim-sh: Coax sh.vim into accepting #/% param expansion
| * Coax sh.vim into accepting #/% param expansionTom Ryder2017-11-151-0/+15
| | | | | | | | These forms of parameter expansion are specified in POSIX sh.
* | Correct URL link function name in HTML ftpluginTom Ryder2017-11-151-2/+2
|/ | | | | I missed the filetype prefix I had added to the function call in the actual declaration of the function itself.
* Correct stray elseif in auto_undodir.vimTom Ryder2017-11-141-1/+1
| | | | | | | | 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
* Move mapleader settings before .vimrc conf sourceTom Ryder2017-11-142-5/+6
| | | | | | | | | | 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.
* Merge branch 'feature/vim-plug' into developTom Ryder2017-11-133-18/+24
|\ | | | | | | | | * feature/vim-plug: Check for shellescape() function before using it
| * Check for shellescape() function before using itTom Ryder2017-11-133-18/+24
| | | | | | | | It was added in patch 111 for Vim 7.0.
* | Strip trailing whitespaceTom Ryder2017-11-135-11/+11
|/
* Force muttrc filetype from ftdetect rulesTom Ryder2017-11-131-1/+1
| | | | | Looks like these were getting categorised as "rc", or "M$ Resource files", in the core filetype.vim.
* Pre-emptively disable core Vim plugins in configTom Ryder2017-11-131-9/+22
| | | | Most of them, anyway. A couple of them are sane and useful.
* Limit \f mapping to normal modeTom Ryder2017-11-131-1/+1
|
* Move 'hlsearch' insert-mode suspension into pluginTom Ryder2017-11-133-14/+76
| | | | | | 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.
* Separate g:loaded/&cp tests from feat testsTom Ryder2017-11-126-6/+24
| | | | | Keeping the tests at the beginning of plugins on one line without continuations is needed to work around &cpo-=C.
* Use :set not :setlocal for 'hlsearch'/'incsearch'Tom Ryder2017-11-121-4/+4
| | | | They don't have local analogues; they're global options.
* Correct nonexistent 'wildmode' value in Vim configTom Ryder2017-11-121-1/+1
| | | | | There is no such setting as "longest:list". What I meant was "list:longest".
* Document each 'backspace' flag in Vim configTom Ryder2017-11-121-3/+8
|
* Mention req of toggle_option_flag.vimTom Ryder2017-11-121-1/+2
|
* Adjust first sentence of format_option_toggle.txtTom Ryder2017-11-121-1/+1
|
* Add help links to toggle_option_flag.vim interfaceTom Ryder2017-11-121-0/+1
|
* Flesh out strip_trailing_whitespace.vim helpTom Ryder2017-11-121-6/+21
|
* Specify type of example in mail_mutt.vim docTom Ryder2017-11-121-3/+3
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-18 07:21:01 +0000