As a newbie to using Tridactyl, I installed the stable version (1.20.4). Anyhow, I tried running the linked installer for the native messenger and noticed that GVim now opens with “fileencoding” set to “latin1”. This resulted in conversion errors (I have “encoding” set to “utf8” in my “vimrc”) but I was able to get around that by running “:x ++enc=utf-8”.

I’m now able to quickly and easily open, close and re-edit text-boxes containing UTF-8 character. Thanks.

Hmm, was it opening with a different file encoding before?

You can `:set editorcmd` to something that gives gVim more commands, like is mentioned in this issue: https://github.com/tridactyl/native_messenger/issues/18

Actually, GVim had been opening with “fileencoding” set to “utf-8” and the contents of the text-box were fine. It was only when saving that the text box would have the wrong characters. Late last Saturday night, I had edited the `editorcmd` to be

    gvim -c "set filetype=markdown fileencoding=latin1"

At that stage, I hadn’t discovered the use of `x ++enc=utf-8` to resolve the issue and gave up at that stage (I thought I had reset the `editorcmd` but must have forgot). Anyhow, with the new native messenger, I don’t need to mess with specifying character sets and I’ve now set the Tridactyl `editorcmd` to the simpler:

    gvim -c "set filetype=markdown"

Now GVIm opens with UTF-8 as both the “encoding” and “fileencoding” so I can exit it as usual with a simple `:x` and the text-box updates correctly.

Thanks again (your help with this prompted me to become a sponsor).

Bah! For some reason, GitHub had “an issue processing your payment method”. I’ll try again tomorrow.