ec16969609
Automatic reparsing of %sh{...}, while convenient in many cases,
can be surprising as well, and can lead to security problems:
'echo %sh{ printf "foo\necho bar" }' runs 'echo foo', then 'echo bar'.
we make this danger explicit, and we fix the 'nop %sh{...}' pattern.
To reparse %sh{...} strings, they can be passed to evaluate-commands,
which has been fixed to work in every cases where %sh{...} reparsing
was used..
18 lines
673 B
Plaintext
18 lines
673 B
Plaintext
hook global BufOpenFile .* %{ evaluate-commands %sh{
|
|
if [ -z "${kak_opt_filetype}" ]; then
|
|
mime=$(file -b --mime-type "${kak_buffile}")
|
|
case "${mime}" in
|
|
application/*+xml) filetype="xml" ;;
|
|
image/*+xml) filetype="xml" ;; #SVG
|
|
message/rfc822) filetype="mail" ;;
|
|
text/x-shellscript) filetype="sh" ;;
|
|
text/x-*) filetype="${mime#text/x-}" ;;
|
|
text/*) filetype="${mime#text/}" ;;
|
|
application/*) filetype="${mime#application/}" ;;
|
|
esac
|
|
if [ -n "${filetype}" ]; then
|
|
printf "set-option buffer filetype '%s'\n" "${filetype}"
|
|
fi
|
|
fi
|
|
} }
|