Open tdillenburg opened 4 years ago
All versions behave consistently and differently from your description for me, but that might be due to a different locale. I can paste ç
to emulate inputting it without trouble. It is displayed and processed correctly.
Is it just displayed like that or characters are transformed into %
/?
on your side? You can check what file ends up being created when statusbar contains a command like :touch <type-problematic-characters-here>
. You can also try pasting name of current file in statusbar with Ctrl-X c.
If I type touch ç
it is displayed as touch %
and outputs the error Too few arguments
. When I copy and paste a file with this characters it adds quotes, for instance "ação"
and I'm unable to paste it back into vifm's command line.
Characters such as
ç
and~
are showing as%
on vifm command line Windows 10 (version 2004). On vifm "window" (not sure about the name) is showing correctly.System locale is set as pt-BR. Neovim is working ok, so I can still
q:
to input comands with this characters. Tested on cmd and cmder (git bash), with builds v0.10.1-323-ge474079382dd and v0.10.1-599-g5b0ee3cd0c6e-dirty. With current release it shows a undefined character ဦ :