For the life of me, I can't seem to get vim to recognize, eg, xHome
and Home as separate keycodes. For instance...
vim -u NONE -N
:set Home? xHome?
t_kh Home ^[[1~
t_kh Home ^[[1~
:set Home=
:set xHome?
E518: Unknown option: xHome?
Is this intentional behavior? What's the point of
Matt Wozniski wrote:
For the life of me, I can't seem to get vim to recognize,
eg, xHome and Home as separate keycodes.
Perhaps the following is an explanation:
:help version7
/xHome
Previously Home and xHome could be mapped separately.
This had the disadvantage that all mappings (with
John Beckett wrote:
Matt Wozniski wrote:
For the life of me, I can't seem to get vim to recognize,
eg, xHome and Home as separate keycodes.
Perhaps the following is an explanation:
:help version7
/xHome
Previously Home and xHome could be mapped separately.
This had the disadvantage
Bram Moolenaar wrote:
Matt Wozniski wrote:
For the life of me, I can't seem to get vim to recognize, eg, xHome
and Home as separate keycodes. For instance...
That's a bug. This patch should fix it:
Yes, that seems to fix it for me, xterm on Linux.
~Matt
Matt Wozniski wrote:
For the life of me, I can't seem to get vim to recognize, eg, xHome
and Home as separate keycodes. For instance...
vim -u NONE -N
:set Home? xHome?
t_kh Home ^[[1~
t_kh Home ^[[1~
:set Home=
:set xHome?
E518: Unknown option: xHome?
Is this