Timeline for Run program on a key press without interupting the key event
Current License: CC BY-SA 3.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:36 | history | edited | CommunityBot | replaced http://unix.stackexchange.com/ with https://unix.stackexchange.com/ | |
| May 24, 2015 at 22:18 | vote | accept | Zorawar | ||
| May 10, 2015 at 2:15 | answer | added | Zorawar | timeline score: 7 | |
| May 9, 2015 at 18:05 | comment | added | Zorawar | @Serg: Yeah, I'm using exactly a work-around like that for now, but I'd like not to. Surely it must be possible. (I'm essentially asking how a keylogger works.) I'm guessing what I want is not to bind the key to some command but instead monitor it via another running program. | |
| May 9, 2015 at 17:42 | comment | added | Sergiy Kolodyazhnyy | Change the shortcut perhaps to something else, like Ctrl+q | |
| May 9, 2015 at 17:39 | comment | added | Sergiy Kolodyazhnyy | I don't see any workaround. Even with xdotool type'q' " . You've basically got infinite loop, where you press and press and press q over and over again, launching that some_command | |
| May 9, 2015 at 17:28 | history | edited | Braiam | CC BY-SA 3.0 | deleted 45 characters in body; edited tags |
| May 9, 2015 at 17:12 | comment | added | Zorawar | @Serg: Yup, that's exactly the problem. When you press 'q' a terminal (or whatever) will open and xdotool simulates another 'q' press. But then that 'q' press gets bound to opening a terminal and xdotool simulates another 'q' press... | |
| May 9, 2015 at 16:37 | comment | added | Sergiy Kolodyazhnyy | Ok, so what I did is I bound "gnome-terminal && xdotool key q" to q and now I have infinitely spawning gnome-terminal. Is that what you're experiencing ? | |
| May 9, 2015 at 16:31 | review | Close votes | |||
| May 9, 2015 at 20:34 | |||||
| May 9, 2015 at 16:25 | history | edited | Zorawar | CC BY-SA 3.0 | added 394 characters in body |
| May 9, 2015 at 16:21 | comment | added | Zorawar | @Serg: yup, but I want the 'q' press to also continue. As it is, some_command replaces the q press. I want the q press to be executed as normal in addition to some_command also being executed. Maybe this wasn't clear in the Q... | |
| May 9, 2015 at 16:18 | comment | added | Sergiy Kolodyazhnyy | So, what exactly you're trying to achieve ? some_command launches some applications and you're trying to make it start with q pressed ? | |
| May 9, 2015 at 16:14 | comment | added | Zorawar | @Serg: I think that Q is not really the same as mine because, well, I know how to run two commands on the same line! Also, I think the solution will not involve running two or more commands after the key has been bound because the loop condition will remain. What I think I need is a completely different solution. I think. | |
| May 9, 2015 at 16:08 | comment | added | Sergiy Kolodyazhnyy | possible duplicate of Associating Multiple Commands with one key in .xbindkeys | |
| May 9, 2015 at 15:55 | history | asked | Zorawar | CC BY-SA 3.0 |