> I can personally confirm that your above mentioned change in
>_vim.py solved the issues I had (without ustf-8 first). However option
>two with setting utf-8 as the first setting works too (without the code
>change).
Interesting. Is somebody able to test a current trunk version of
UltiSnips? Maybe your troubles are fixed there already as I made
UltiSnips a bit cleverer concerning vim encodings.
>Hey Silver,
The name's SirVer, mr. redeyes.
> I can personally confirm that your above mentioned change in
>_vim.py solved the issues I had (without ustf-8 first). However option
>two with setting utf-8 as the first setting works too (without the code
>change).
Interesting. Is somebody able to test a current trunk version of
UltiSnips? Maybe your troubles are fixed there already as I made
UltiSnips a bit cleverer concerning vim encodings.