vim-vebugger icon indicating copy to clipboard operation
vim-vebugger copied to clipboard

bugfix for "language message" in MacOSX

Open jayli opened this issue 6 years ago • 6 comments

Error detected while processing function <SNR>85_readingTimerCallback[1]..378[13]..379[10]..370[16]..vebugger#std#updateMarksForFile[5] ..vebugger#util#listSignsInBuffer[1]..<SNR>83_listSigns[2]..vebugger#util#EnglishExecute: line 3: E197: Cannot set language to "en_US.utf8"

jayli avatar Sep 28 '18 04:09 jayli

@kyouryuukunn added this part in #69 to fix a bug with non-english environments. The whole idea - if I understood it correctly - is to set the language to english to avoid that bug in Japanese Vim. If you set it to l:lang that just becomes a big NOP - it does nothing (sets the language to itself) and @kyouryuukunn 's bug returns.

I don't have a mac, nor a Japanese machine (and I'm not going to set my machine to Japanese and lock myself out because I can't set it back...), but I googled a bit and it looks like en_US.utf8 is an alias to en_US.UTF-8 and not all setups accept that alias. So:

  • @jayli - I assume :language language messages en_US.utf8 doesn't work for you, but what happens when you run :language language messages en_US.UTF-8?
  • @kyouryuukunn - Does :language language messages en_US.UTF-8 work for you?

I think en_US.UTF-8 is the canonic locale, so if it works for everyone the fix will be to just use that.

As for using exec when restoring the language - I have no idea how it worked without it in the first place...

idanarye avatar Sep 28 '18 13:09 idanarye

dosn't work, it shows me this E197: Cannot set language to "language messages en_US.UTF-8"

jayli avatar Sep 30 '18 05:09 jayli

Me too. 'language messages en_US.UTF-8' isn't work in my windows 10 x64

kyouryuukunn avatar Oct 05 '18 10:10 kyouryuukunn

Sorry, previous comment is miss. en_US.UTF-8 works correctly.

kyouryuukunn avatar Oct 05 '18 10:10 kyouryuukunn

I re-implement it https://github.com/jayli/vim-easydebugger

jayli avatar Oct 26 '18 04:10 jayli

@idanarye I ran into this problem too and if set the language to en_US.UTF-8 it works on my Mac. I'm going to check the situation on my Arch machine later but I assume this should work there as well. If so, shall I craft a new PR, so we get that merged finally?

As a sidenote: are you still sort of maintaining this project? These many stalled PR's made me wonder... You probably wanne close those PR's like this one? 🤷‍♂ :)

Edit: on my Arch system it's the same. I had to add the en_US.UTF-8 locale first but then it works fine

skriems avatar Apr 04 '20 10:04 skriems