aboutsummaryrefslogtreecommitdiff
path: root/vim/ftdetect
diff options
context:
space:
mode:
authorTom Ryder <tom@sanctum.geek.nz>2017-11-08 11:57:21 +1300
committerTom Ryder <tom@sanctum.geek.nz>2017-11-08 12:44:59 +1300
commitac577df9f6516308c2f9661c8abbc44f6c19d854 (patch)
tree5dbb56b651377ac9745d140491e01f6a47cc991f /vim/ftdetect
parentMerge branch 'hotfix/v0.11.1' into develop (diff)
downloaddotfiles-ac577df9f6516308c2f9661c8abbc44f6c19d854.tar.gz
dotfiles-ac577df9f6516308c2f9661c8abbc44f6c19d854.zip
Use sh.vim local vars not global POSIX hacks
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.
Diffstat (limited to 'vim/ftdetect')
0 files changed, 0 insertions, 0 deletions