rst byte is 0x8e)
But in display phase, the next 0xNN character is displayed WITHOUT 0x8e.
It messes up a vim screen / terminal emulator.
The 0x8e character should be displayed prior to the 0xNN.
Here is a simple patch to fix it.
I'm not sure that the patch is a good fix, but it works f
h is the best way, so I made this patch to see what happen.
I repeat this is just a PoC code.
The patch is not tested enough yet, and it may be wrong.
Moreover, I'm not using gvim nor Windows. I tested only on FreeBSD.
And I'm not good at Vim source code, so I hope someone fix it.
Best r
ut this feature / problem, everyone?
Bram, could you add this *feature* to Vim if you think it's good, please?
# ofcourse, you don't have to use the patch.
And, let me know if there's something I can do.
Thanks in advance.
Best Regards,
Kikuchan
--
You received this message from t
patch adds the thin translation layer described above.
The translation is done everytime when Vim trying to interact with filesystem,
or Vim trying to execute a shell command.
# I'm sorry a previous version of patch have a double-free bug...
Bram, could you include the patch for beta test
#x27; key, like 'dup' key.
Bram, could you include this harmless feature, please? ;)
See the attached patch for more details.
It's very simple, and it doesn't change any default behavior.
Thanks in advance.
Best Regards,
Kikuchan
--
You received this message from the "vim
