key command not working in chained command about xdotool HOT 3 OPEN

On Sat, Mar 25, 2023 at 7:19 PM Jordan Sissel ***@***.***> wrote: Then I tried opening another terminal window, and running: ***@***.*** ~]$ xdotool search --class gnome-terminal key --window %@ a ***@***.*** ~]$ and nothing happened in either terminal. This can sometimes happen and most of the time it is because the program is intentionally ignoring the keypress events sent by xdotool. GTK apps appear to do this by default, for example, such as gnome-terminal and Firefox. You can read more about this in the xdotool manpage under SENDEVENT NOTES if you want to know more about the phenomenon. The best workaround I can offer is to send keyboard events only to the currently-active window. If you need to send keyboard events to multiple windows using this technique, you'll need to have xdotool search provide you a list of windows and then activate each window (bringing it forward and giving it focus for your keyboard/mouse events) and *then* send keystrokes. For example: xdotool search --class gnome-terminal key | xargs -I@ -n1 xdotool windowactivate --sync @ type hello This uses sends the list of window identifiers to a tool called xargs which will run xdotool for each window identifier printed by xdotool and uses '@' as a placeholder for the window identifier for each xdotool run. The commands it runs uses: - windowactivate --sync -- this activates one window and waits for it to be the activated window - type hello this will send 'hello' to the active window as a sequence of keyboard events Hope this helps! — Reply to this email directly, view it on GitHub <#422 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6IJW6FMSEW2YTF5RRGHCUTW57GULANCNFSM6AAAAAAWGFTUVY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Hi Jordan, Wow, thanks for getting back to me with these helpful instructions! I will definitely try it out. I appreciate it! Thanks, Adam On Sat, Mar 25, 2023 at 7:19 PM Jordan Sissel ***@***.***> wrote: > Then I tried opening another terminal window, and running: > > ***@***.*** ~]$ xdotool search --class gnome-terminal key --window > %@ a > ***@***.*** ~]$ > > and nothing happened in either terminal. > > This can sometimes happen and most of the time it is because the program > is intentionally ignoring the keypress events sent by xdotool. GTK apps > appear to do this by default, for example, such as gnome-terminal and > Firefox. You can read more about this in the xdotool manpage under SENDEVENT > NOTES if you want to know more about the phenomenon. > > The best workaround I can offer is to send keyboard events only to the > currently-active window. If you need to send keyboard events to multiple > windows using this technique, you'll need to have xdotool search provide > you a list of windows and then activate each window (bringing it forward > and giving it focus for your keyboard/mouse events) and *then* send > keystrokes. > > For example: > > xdotool search --class gnome-terminal key | xargs -I@ -n1 xdotool windowactivate --sync @ type hello > > This uses sends the list of window identifiers to a tool called xargs > which will run xdotool for each window identifier printed by xdotool and > uses '@' as a placeholder for the window identifier for each xdotool run. > > The commands it runs uses: > > - windowactivate --sync -- this activates one window and waits for it > to be the activated window > - type hello this will send 'hello' to the active window as a > sequence of keyboard events > > Hope this helps! > > — > Reply to this email directly, view it on GitHub > <#422 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/A6IJW6FMSEW2YTF5RRGHCUTW57GULANCNFSM6AAAAAAWGFTUVY> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >