-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KEY_LEFT KEY_RIGHT and KEY_HOME don't work in separate st with abduco #116
Comments
A small update after some testing. It would appears that keys that stop working when re-attached via a different st instance include: KEY_IC, KEY_DC, KEY_HOME, KEY_END, KEY_LEFT, KEY_RIGHT, KEY_UP, and KEY_DOWN. However, note that KEY_PPAGE and KEY_NPAGE continue to work! (I.e., I can set #define MOD KEY_PPAGE and it will work fine, but, e.g., #define MOD KEY_IC will not.) I still haven't found any rhyme or reason why that set of keys would be signaled out... |
Three small updates (still debugging this): |
I tried to reproduce this problem but I could not. It works fine for me. I am using: abduco-0.6 © 2013-2018 Marc André Tanner dvtm-v0.15-52-g7bcf43f © 2007-2016 Marc André Tanner st 0.8.4 |
This is an odd problem. I'm still finding the exact case where this happens.
Basically, to duplicate:
in config.h bind some key to the right/up/down/left arrow or home, e.g.
{ { MOD, KEY_DOWN, }, { focusdown, { NULL } } },
{ { MOD, KEY_UP, }, { focusup, { NULL } } },
launch st
abduco -c test
within this instance, up/down work as expected.
launch a separate st
abduco -a test
within this instance, up/down do not work as expected.
I've tested this with dtach instead of abduco, with xterm (and console) instead of st. So I've narrowed it down to something funky in dvtm. However, that's as far as I've gotten.
FWIW, env in both st instances is the same except WINDOWID.
FWIW, oddly the KEY_PPAGE works fine (one of the defualt bindings)
Thanks in advance for any help on this.
The text was updated successfully, but these errors were encountered: