3 ms·
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
by bovine3dom 6y ago
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 https://github.com/tridactyl/native_messenger/issues/18
- Anthony-G 6y agoActually, 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).
- Anthony-G 6y agoBah! For some reason, GitHub had “an issue processing your payment method”. I’ll try again tomorrow.