aboutsummaryrefslogtreecommitdiff
path: root/vim/config/syntax.vim
diff options
context:
space:
mode:
authorTom Ryder <tom@sanctum.geek.nz>2017-10-30 19:11:22 +1300
committerTom Ryder <tom@sanctum.geek.nz>2017-10-30 19:11:22 +1300
commit1834c083aa436d59713b0054566e06648d67ac1e (patch)
treec49418442110da13aef79acfb7af29eee95ab4b1 /vim/config/syntax.vim
parentMove viminfo conf from spell.vim into new subfile (diff)
downloaddotfiles-1834c083aa436d59713b0054566e06648d67ac1e.tar.gz
dotfiles-1834c083aa436d59713b0054566e06648d67ac1e.zip
Apply name conventions, scoping to Vim identifiers
The Google VimScript Style Guide says <https://google.github.io/styleguide/vimscriptguide.xml#Naming>: >In general, use plugin-names-like-this, FunctionNamesLikeThis, >CommandNamesLikeThis, augroup_names_like_this, >variable_names_like_this. Adjusted variable, function, and `augroup` names accordingly, including setting script scope for some of the functions and their calls (`s:` and `<SID>` prefixes). Initially I tried using `prefix#`, but it turns out that this is a namespacing contention for publically callable functions like `pathogen#infect`, and none of these functions need to be publically callable.
Diffstat (limited to 'vim/config/syntax.vim')
-rw-r--r--vim/config/syntax.vim4
1 files changed, 2 insertions, 2 deletions
diff --git a/vim/config/syntax.vim b/vim/config/syntax.vim
index 08b908c8..e7d94b1b 100644
--- a/vim/config/syntax.vim
+++ b/vim/config/syntax.vim
@@ -10,7 +10,7 @@ if has('syntax')
if has('eval') && v:version >= 701
" Wrap all this logic in a function
- function! DetectBackground()
+ function! s:DetectBackground()
" Split up the value of $COLORFGBG (if any) by semicolons
let l:colorfgbg = split($COLORFGBG, ';')
@@ -28,7 +28,7 @@ if has('syntax')
endfunction
" Call the function just defined directly
- call DetectBackground()
+ call s:DetectBackground()
" Ancient or cut-down Vim? Just go dark
else