xenia/kakoune
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Simplify handlebars adding/removal hooks

Browse Source 
Removing the handlebars highlighters when a client toggles away from hbs window unintentionally causes
other clients attached to hbs windows to no longer highlight correctly.  The only other option is to
copy the entire html highlighter and all of it's rules, but that seems like a maitenance headache.
So instead, just leave the hbs rules injected into the html rules once the user opens any handlebars file.
It's not ideal, but I'd say it's the least bad option.
This commit is contained in:
Matt Schick 2018-10-06 08:39:01 -05:00
parent eba40028b9
commit 8e698e0054
1 changed files with 1 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
rc/extra/hbs.kak
View File

@ -80,29 +80,8 @@ define-command -hidden maybe-add-hbs-to-html %{ evaluate-commands %sh{
fi fi
} } } }
define-command -hidden remove-hbs-from-html %{
remove-highlighter shared/html/hbs
remove-highlighter shared/html/tag/hbs
set-option global hbs_highlighters_enabled false
}
# The two hooks below are wrapped in this "-once" so that they only get enabled
# when atleast one .hbs file is opened. This way people who don't edit .hbs files
# aren't paying a performance penality of these hooks always executing.
hook -once global BufCreate .*\.(hbs) %{
hook -group hbs-highlight global WinDisplay .*\.(hbs) %{ evaluate-commands %sh{
if [ "$kak_opt_filetype" = "hbs" ]; then
printf %s "maybe-add-hbs-to-html"
fi
} }
hook -group hbs-highlight global WinDisplay .*\.(?!hbs).* %{
remove-hbs-from-html
}
}
hook -group hbs-highlight global WinSetOption filetype=hbs %{ hook -group hbs-highlight global WinSetOption filetype=hbs %{
maybe-add-hbs-to-html
add-highlighter window/hbs-file ref hbs-file add-highlighter window/hbs-file ref hbs-file
} }