quicktile VS xdotool

You might wanna have a look at quicktile. It's basically an addon that adds tiling to existing WM. Works well, but lacks some of the intrgrations dedicated tiling WM have.

As the author of QuickTile, which is written in Python but even closer to what you describe than a window manager would be, I have to say that, yeah, doing X11 stuff takes a lot of knowledge that's not ideally documented in non-print sources.

quicktile is a handy tiling tool which saves me a lot of time. native custom tiling is always better tho

It's been a long time since I bothered with this functionality, but I seem to recall that quicktile was a better fit for me than those other two. Not sure if it's still viable.

Actually, I plan to add a .nojekyll file and then use something like Pelican with custom plugins, then set GitHub Actions to run my update.sh on push... similar to how http://ssokolow.com/quicktile/ is a Sphinx-based site hosted on GitHub Pages and automatically regenerated from the pushed sources.

I've been using ssokolow.com/quicktile for this purpose, it does what I need and doesn't replace the wm.

If you're into using shortcuts I would recommend installing Quicktile for manage your windows: https://github.com/ssokolow/quicktile

you can try quicktile

The best I could do for the API documentation for this project of mine was to use the automodule directive to autogenerate at the coarsest level possible and remember to never create new .py files if I could possibly avoid it.

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)