Welcome to Vifm Q&A, where you can ask questions about Vifm usage. Registration is optional, anonymous posts are moderated. GitHub or Google logins are enabled.
0 votes
in vifm by
by

What's your locale? I.e. output of locale in terminal.

by

en_US.utf8
I have no problems with those symbols outside of vifm tho.

1 Answer

+1 vote
by
selected by
 
Best answer

Codes of these characters match special keys of ncurses, namely KEY_BTAB and KEY_BACKSPACE, that's why they aren't handled as usual input.

I'm quite surprised that this issue wasn't found before, but it seems to be solvable. I'll just move all special keys to Unicode Private Use Area starting from U+E000, which shouldn't clash with anything except for maybe iconic fonts, but by convention they start from U+F000, so even that shouldn't happen. (Solution that guarantees no clashes ever is possible, but very inconvenient for implementation.)

There is no workaround for now, you'll have to rename such files on the shell. Development version will get the fix soon, just need to make sure I don't introduce new bugs by editing 500+ lines.

Thanks for the report!

by

Thanks a lot for looking into this.

If you would like to make a bug report or feature request consider using GitHub, SourceForge or e-mail. Posting such things here is acceptable, but this is not a perfect place for them.
...