diff options
author | Tom Ryder <tom@sanctum.geek.nz> | 2018-12-27 00:02:49 +1300 |
---|---|---|
committer | Tom Ryder <tom@sanctum.geek.nz> | 2018-12-27 00:02:49 +1300 |
commit | 5fc2b40d7b54f6aaedf6760c2d537258c14d3c23 (patch) | |
tree | e2120efb3a3020cca360de25e8e791b901881bc5 | |
parent | Two-space sentences in shell comments (diff) | |
download | dotfiles-5fc2b40d7b54f6aaedf6760c2d537258c14d3c23.tar.gz dotfiles-5fc2b40d7b54f6aaedf6760c2d537258c14d3c23.zip |
Two-space sentences in VimL comments
-rw-r--r-- | vim/after/syntax/sh.vim | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/vim/after/syntax/sh.vim b/vim/after/syntax/sh.vim index bdedaf65..95ec5546 100644 --- a/vim/after/syntax/sh.vim +++ b/vim/after/syntax/sh.vim @@ -20,12 +20,12 @@ endif syntax clear shDerefWordError " The syntax highlighter doesn't match parens for subshells for 'if' tests -" correctly if they're on separate lines. This happens enough that it's +" correctly if they're on separate lines. This happens enough that it's " probably not worth keeping the error. syntax clear shParenError " 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 +" 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. syntax clear shTestError @@ -33,8 +33,8 @@ syntax clear shTestError if exists('b:is_posix') " Highlight some commands that are both defined by POSIX and builtin - " commands in dash, as a rough but useable proxy for 'shell builtins'. This - " list was mostly wrested from `man 1 dash`. Also include control structure + " commands in dash, as a rough but useable proxy for 'shell builtins'. This + " list was mostly wrested from `man 1 dash`. Also include control structure " keywords like `break`, `continue`, and `return`. syntax clear shStatement syntax cluster shCommandSubList add=shStatement @@ -76,7 +76,7 @@ if exists('b:is_posix') " Core syntax/sh.vim puts IFS and other variables that affect shell function " in another color, but a subset of them actually apply to POSIX shell too - " (and plain Bourne). These are selected by searching the POSIX manpages. I + " (and plain Bourne). These are selected by searching the POSIX manpages. I " added NLSPATH too, which wasn't in the original. syntax clear shShellVariables syntax cluster shCommandSubList add=shShellVariables @@ -112,7 +112,7 @@ if exists('b:is_posix') \ PWD " Core syntax/sh.vim thinks 'until' is a POSIX control structure keyword, - " but it isn't. Reset shRepeat and rebuild it with just 'while'. I only + " but it isn't. Reset shRepeat and rebuild it with just 'while'. I only " sort-of understand what this does, but it works. syntax clear shRepeat syntax region shRepeat @@ -127,7 +127,7 @@ if exists('b:is_posix') " ${foo%bar}, ${foo%%bar}, ${foo#bar}, and ${foo##bar} are all valid forms " of parameter expansion in POSIX, but sh.vim makes them conditional on - " Bash or Korn shell. We reinstate them (slightly adapted) here. + " Bash or Korn shell. We reinstate them (slightly adapted) here. syntax match shDerefOp contained \ '##\|#\|%%\|%' \ nextgroup=@shDerefPatternList @@ -150,7 +150,7 @@ if exists('b:is_bash') syntax clear bashAdminStatement " Reduce bashStatement down to just builtins; highlighting 'grep' is not - " very useful. This list was taken from `compgen -A helptopic` on Bash + " very useful. This list was taken from `compgen -A helptopic` on Bash " 4.4.5. syntax clear bashStatement syntax keyword bashStatement |