Welcome to Vifm Q&A, where you can ask questions about using Vifm. Registration is optional, anonymous posts are moderated. E-mail and GitHub logins are enabled.
0 votes
in vifm by
edited by

I am very impressed with vifm capabilities, however I have found some strange behavior when pressing F3 and F4 in normal mode. Pressing F3 does nothing, and pressing F4 brings up the sort option dropdown menu, although vifmrc specifies nnoremap <f3> :!less %c<cr> and nnoremap <f4> :edit %c<cr>. However, the :edit %c command works correctly: it opens the file in vim. The terminal is xterm-color, the $TERM variable is set via .Xresources and has the correct value (xterm-color). I would be glad if someone could explain what is wrong.

1 Answer

0 votes
by
selected by
 
Best answer

I'm not sure what xterm-color terminfo entry is for and why it's defined this way, but it uses definitions of functional keys that don't match what XTerm is actually sending:

[~]$ infocmp xterm-color xterm-256color | grep 'kf[34]:'
        kf3: '\E[13~', '\EOR'.
        kf4: '\E[14~', '\EOS'.
[~]$ Ctrl+V F3: ^[OR
[~]$ Ctrl+V F4: ^[OS

Using xterm or xterm-256color should work fine. There may be a configuration option for XTerm which makes it compatible with xterm-color.

by

Thank you very much for your prompt reply. That's all I needed.

by

Switched to xterm-256color. Everything works.

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.
...