owl VS xdotool

Well, there is a Wayland Compositor for macOS:

https://github.com/owl-compositor/owl

It still lacks a lot of features though (I think, I never tried it out)

> X runs on so many more platforms than Wayland [...] Python3 is strictly an improvement on every platform, I don't think they're analogous because there really is no good reason to keep Python2 around

X runs on more platforms than Wayland because...it was ported to them. Just like things use Python 3 because they were ported to it.

This is also understating the reach of X I think: it's widely used in the embedded world, is seeing increasing support in BSDs, and has even been used on macOS (https://github.com/owl-compositor/owl). People have even used it to embed an entire compositor inside a GTK app (https://github.com/alexlarsson/wakefield).

That isn't to say that libwayland has a lot of Linux-isms in it, but afaik they're not really structural as much as there is lack of interest to generalize things more. Heck, the protocol-oriented architecture would even make it easier for anything Linux-esque to be removed in favor of alternative protocols.

Yup, the Owl compositor implements Wayland on Quartz (the macOS graphics system).

Thanks! FYI there is a wayland compositor for macos too, so it would be nice to be able to use that with linux apps in a VM...

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)