key-mapper VS xdotool

This may help you!

Another option is key-mapper which runs as a systemd service and lets you map all kinds of things to other things.

Key-mapper

Being a previous windows user I have a mindset that I shouldn't download non mainstream or non trusted applications on my system especially the ones that have admin access or physical device access . I wanted to remap my keyboard in such way which allows me to use capslock key as backspace and alt_r key as escape. setxkbmap and Xmodmap isn't giving required results or I am not too advance to use it properly . I recently stumbled upon this program key-mapper but it requires admin access so should I trust it for daily use. ( I am not a developer and thus does not understand what any of the code does )

There's Key Mapper which I haven't tried yet (still on my 100% rubberdome at the moment so no need) but it looks very promising.

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)