I use workspaces a lot in Ubuntu. Usually, 1 workspace with onivim, and over it firefox or something like this. There is a really annoying quirk when doing it this way though. When moving up to the workspace with firefox from oni2 using crtl alt UP, everything is fine and I land well in firefox. However, moving down with ctrl alt DOWN, it seems like the ctrl alt DOWN keystroke gets interpreted by oni2 as a motion, and my cursor location gets changed inside the oni2 buffer.
This is really very annoying to live with in daily life, as this means that there is a "cognitive bias" introduced for example switching from StackOverflow to my code back and forth.
Any way / hope to get this ironed out? It looks like oni2 correctly detects that the keystroke is ctrl alt ARROW, so I get "blacklisting" all ctrl alt ARROW motions would do the trick (of course ARROW could in general be up, down, right, left).
That would make my life much easier day to day :) .
I use workspaces a lot in Ubuntu. Usually, 1 workspace with onivim, and over it firefox or something like this. There is a really annoying quirk when doing it this way though. When moving up to the workspace with firefox from oni2 using
crtl alt UP
, everything is fine and I land well in firefox. However, moving down withctrl alt DOWN
, it seems like thectrl alt DOWN
keystroke gets interpreted by oni2 as a motion, and my cursor location gets changed inside the oni2 buffer.This is really very annoying to live with in daily life, as this means that there is a "cognitive bias" introduced for example switching from StackOverflow to my code back and forth.
Any way / hope to get this ironed out? It looks like oni2 correctly detects that the keystroke is
ctrl alt ARROW
, so I get "blacklisting" allctrl alt ARROW
motions would do the trick (of course ARROW could in general be up, down, right, left).That would make my life much easier day to day :) .