Closed thomashoullier closed 1 month ago
I can reproduce:
$ ./nnn -K
key collision! [^M]
key collision! [c]
@jacmoe what do you suggest?
Note the gentoo maintainers apply another patch to this patch, as seen here.
AFAIK that's backporting a fix in master
. It's unrelated to your issue.
@thomashoullier do you (or any other colemak user) have any suggestion on what to change here?
I use colemak-dh so h(as host) is ok for me. But that would clash with classic colemak. I suggest make it capital C.
Thank you for the responses. I have no suggestion to make as I am not running colemak per-se and rebind many keys using my own patch. I simply noticed your colemak patch created the key collision in question and wanted to warn about the problem.
@Darukutsu any suggestion for Ctrl+m
(filter mode)?
(EDIT: went with Ctrl+k
for it.)
Environment details
NNN_TRASH=2
nnn
masterI compiled the latest nnn package revision from the gentoo repository with the
colemak
USE flag which enables the Colemak patch.I noticed the keybind for
SEL_NEW
in the patch (to the keyc
) clashed with the vanilla keybind forSEL_REMOTE
(also set toc
). This collision is detected bynnn -K
. When I ran nnn, thec
key was bound toSEL_REMOTE
and I could not access the "create" feature.I solved the problem on my installation by adding my own patch which removes the binding for
SEL_REMOTE
entirely. I don't think this solution is applicable to all colemak users. Maybe the colemak bindings patch needs to be adjusted so that bothSEL_REMOTE
andSEL_NEW
are accessible?Note the gentoo maintainers apply another patch to this patch, as seen here. I am not sure what this is about, but it seems related to the keybinds documentation only. This is probably a separate issue.