that's all rather, heavily dependent on lucky combination of at least 2-3 mappings - what 1) X-server/graphical-env converts your keyboard into, then what 2) co

that's all rather, heavily dependent on lucky combination of at least 2-3 mappings - what 1) X-server/graphical-env converts your keyboard into, then what 2) console/terminal converts that into, and then what 3) app (vim or bash or whatever) running inside terminal, decides to map (and there maybe more layers before, inside, after or instead of these - e.g. hoping 0) kernel transparently passing stuff to 1). e.g. If running without X/graphics, then first is replaced by kernel's keyboard processing ; or if running graphical Vim, then 2+3 are replaced.. (ah, and the dual/multi mode-ness of vim adds extra layer inside it - making say ctrl-U to do undo always isn't that easy) Each of those layers can vary, in different distro's, terminals, versions of same thing, etc. Especialy each and every (X-)terminal-thingie having different idea of how to map (or not) ctrl-F2. Some of them going back to the 197x .. i have tried to make myself a one-mapping-fits-all (say, pressing F2 does ls -alF in terminal+shell, and saves-the-buffer in vim, no matter what/where/when), collecting variants and combinations for last ~25+ years - incl. linux-console and even dos mapping.. and it works mostly.. but still, no silver bullet. see the qini/ folder in https://github.com/svilendobrev/svd_bin https://github.com/svilendobrev/svd_bin everything may be remapped to your liking.. eventually. YMMV. ciao & have fun