wtype VS xdotool

You need to have wtype installed

Take a look at ydotool and wtype. AFAIK they're the best options at the moment.

ydotool & wtype are able to click/type and automate input on wayland

Maybe try wtype ?

wtype

wtype - xdotool type for wayland

tessen can use either bemenu, the wayland fork of rofi, or wofi to show password store data. It relies on wtype for autotyping instead of using ydotool because ydotool needs root privileges.

I've made a script called tessen which is, more or less, a replacement of rofi-pass but for Wayland. It can use bemenu or the wayland fork of rofi. It relies on wtype for autotyping instead of using ydotool because ydotool needs a daemon running with root privileges.

Have a look at this: https://github.com/jordansissel/xdotool

Maybe not AHK exactly, but it essentially does the same: xdotool

Use an external tool, like xdotool.

In a gtk-rs application, I'm running a xdotool command to get the id of the application's window. I'm running the command in a connect_show closure (after the window has been shown):

Eventually, I needed to find the ID of windows, move them, and bring them to the front—I realized I couldn't do that with gtk-rs. I needed to interact with the window manager (X11 server). So from inside my application, I ran commands that called xdotool.

You might be able to use audacity in the background by setting up an application launcher in the gnome panel that executes xdotool, which can send keyboard signals (like R for record) to running applications: https://github.com/jordansissel/xdotool

Right now, I'm focusing (switching) X11 windows with a shell command (xdotool) from inside my Rust program:

Maybe xdotool [0] is what you're looking for.

[0] https://github.com/jordansissel/xdotool/

I often create screen recordings for my classes, but it's very boring and time consuming. I'm a perfectionist, and if I mistype a command I prefer to re-record everything. Moreover, every time one of the tools used in the videos gets a significant update, I feel compelled to redo the video.

I have started using xdotool [1] to create bash scripts that send mouse clicks and keystrokes to apps. Interleaving calls to xdotool with the "sleep" command [2] produce a convincing effect. If I need to redo a video to fix typos or after a program update, I just fix the bash script and restart the recording.

Alas, the only thing that is missing in my videos is the sound of keyboard clicks… But nothing is perfect!

[1] https://github.com/jordansissel/xdotool

[2] https://en.wikipedia.org/wiki/Sleep_(command)