aboutsummaryrefslogtreecommitdiff
path: root/vim/after/syntax
Commit message (Collapse)AuthorAgeFilesLines
* Don't color colon-delimited labels in Vim commentsTom Ryder2019-11-091-1/+3
|
* Break a long lineTom Ryder2019-06-071-1/+3
|
* Get full path before testing for :CompilerSetTom Ryder2019-05-291-1/+1
|
* Limit :CompilerSet coloring to compiler/*.vimTom Ryder2019-05-291-16/+20
|
* Color Vim script :CompilerSet commands betterTom Ryder2019-05-291-0/+17
|
* Break up long lines in sh syntax fileTom Ryder2019-05-171-2/+10
|
* Remove unnecessary g: prefixes to Vim variablesTom Ryder2019-05-092-3/+3
|
* Two-space sentences in VimL commentsTom Ryder2018-12-271-8/+8
|
* Remove highlight double-quote VimL comment stringsTom Ryder2018-12-261-0/+2
|
* Require Vim 7 for filetype and syntax highlightsTom Ryder2018-11-301-5/+0
| | | | | | It's time! The rest of the vimrc can probably be allowed to load, though.
* Simplify a load guard for sh.vim syntax tweaksTom Ryder2018-11-291-3/+2
|
* Remove some Vim syntax boilerplateTom Ryder2018-11-293-18/+0
|
* Add Bash settings to Vim readline highlightingTom Ryder2018-11-161-0/+3
| | | | | This includes the creation of a hitherto-unneeded Makefile target install-vim-syntax.
* Ignore unset variables in sh.vim clear scriptTom Ryder2018-11-011-1/+1
| | | | | | | | | Error message is: Error detected while processing /home/tom/.vim/after/syntax/sh.vim: line 10: E108: No such variable: "g:is_kornshell" Press ENTER or type command to continue
* Test for g:is_posix existence before purgeTom Ryder2018-08-221-1/+3
|
* Add load guard to bindzone.vim syntax extensionsTom Ryder2018-08-221-0/+6
|
* Fix SSHFP/TLSA record highlighting in bindzone.vimTom Ryder2018-08-221-0/+3
|
* Simplify g:is_posix unset, add g:is_kornshellTom Ryder2018-08-151-4/+1
|
* Unset g:is_posix when no longer neededTom Ryder2018-08-151-0/+7
|
* Add compatible/version guard to syntax after filesTom Ryder2018-07-193-10/+16
|
* Highlight overly long Git commit subjects as errorTom Ryder2018-07-081-0/+2
|
* 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.
* 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
|
* 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
|
* Coax sh.vim into accepting #/% param expansionTom Ryder2017-11-151-0/+15
| | | | These forms of parameter expansion are specified in POSIX sh.
* Remove false error flagging for sh char class globTom Ryder2017-11-091-0/+5
| | | | | | 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.
* Fix 'while'/'until' highlighting in syntax/sh.vimTom Ryder2017-11-091-0/+14
| | | | | | | 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).
* Add clustering for POSIX shell syntax groupsTom Ryder2017-11-081-0/+3
| | | | | | 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.
* Add `kill` as shStatementTom Ryder2017-11-081-0/+1
| | | | | It's not a shell builtin in `dash`, but it is in `Bash`, and I kind of think of it that way.
* Add `break`, `continue`, `return` as shStatementTom Ryder2017-11-081-1/+5
|
* Override commands and variables for syntax/sh.vimTom Ryder2017-11-081-0/+76
| | | | | | | | | | The defaults for these groups don't make much sense to me, so I completely reset them. This isn't quite complete yet; for some reason as soon as e.g. an IFS= setting is contained in e.g. an "if" or "while" block, they don't highlight correctly anymore. There's probably some other part of the core syntax/sh.vim file I need to include here.
* Disable unwanted shell error syntax for any shellTom Ryder2017-11-081-12/+7
|
* Use sh.vim local vars not global POSIX hacksTom Ryder2017-11-081-7/+9
| | | | | | | | | | | | | | | | | | | Rather than setting g:is_posix and working around core syntax/sh.vim's ideas about Korn and POSIX shells, forego sh.vim's efforts to guess what shell the system /bin/sh is entirely. It's irrelevant to me anyway, since I'll often be writing shell scripts to run on an entirely different system. Instead, if we have a #!/bin/sh shebang reflected in the b:is_sh variable set by core filetype.vim, and we don't have any other buffer-level indication of what shell this is, assume it's POSIX, because I very rarely write Bourne. Then, after the syntax file is loaded, clear away all but one of the resulting b:is_* variables. I have a feeling this is going to end with me re-implementing this syntax file, possibly as separate sh.vim, bash.vim, and ksh.vim files.
* Correct variable name in commentTom Ryder2017-11-011-3/+2
| | | | | | This was unintentionally committed in e36efd4. The correct name of the variable is b:is_ksh. b:is_kornshell_proper was a rejected first revision of the name.
* Remove extraneous spacing between wordsTom Ryder2017-11-011-1/+1
| | | | No functional effect.
* Rearrange and better explain ksh syntax workaroundTom Ryder2017-10-301-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | Move the rule setting the custom b:is_ksh variable used for this workaround (established in 52615f6) into an ftplugin file, rather than into ftdetect; the latter seems a much more appropriate place since by this point we've definitely decided the file type is "sh". From the revised comment in this changeset: >Setting g:is_posix above also prompts Vim's core syntax/sh.vim script >to set g:is_kornshell and thereby b:is_kornshell to the same value as >g:is_posix. > >That's very confusing, so before it happens we'll copy b:is_kornshell's >value as determined by filetype.vim and ~/.vim/ftdetect/sh.vim into a >custom variable b:is_ksh, before its meaning gets confused. > >b:is_ksh as a name is more inline with b:is_bash and b:is_sh, anyway, >so we'll just treat b:is_kornshell like it's both misnamed and broken. > >We can then switch on our custom variable in ~/.vim/after/syntax/sh.vim >to apply settings that actually *are* unique to Korn shell and its >derivatives.
* Correct a path in vim/after/syntax/sh.vimTom Ryder2017-10-301-3/+2
| | | | | This and the other files in the now-removed vim/after/ftdetect directory were moved to vim/ftdetect in f8af47b.
* Still untangling the shell highlighting messTom Ryder2016-12-111-0/+98
|
* Reset most of my sh.vim customizationsTom Ryder2016-12-111-77/+0
| | | | | | There's been a lot of work done to sh.vim since these customisations were made, and I can't remember why I made some of them. I'll work without them for a while and reapply any of them if needed.
* Remove mail syntax after file for VimTom Ryder2016-03-311-10/+0
| | | | Turned out to be a bad idea.
* Remove blank lines at end of filesTom Ryder2016-03-285-5/+0
|
* Refactor ed() wrapper, add rlwrap(1)Tom Ryder2016-03-161-0/+11
|
* Stop highlighting syslog errorsTom Ryder2015-07-271-0/+4
|
* Add a few missing Bash keywordsTom Ryder2015-06-041-0/+3
|
* Move syntax rules from sahara.vim to .vim/afterTom Ryder2015-06-042-0/+7
|
* Exclude some builtins I added to sh.vimTom Ryder2014-10-301-6/+3
| | | | | Refine previous commit a little to restore some of the weirdness I actually do like
* Fix a few more annoyances in sh.vim syntaxTom Ryder2014-10-301-0/+68
|
* Fix simpleDeRef in sh.vimTom Ryder2014-10-301-0/+10
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-01-13 20:13:33 +0000