auto-tab-discard VS xdotool

You might want to ask on developer of the addon: https://add0n.com/tab-discard.html

Not to be an enabler or anything, but have you tried Auto Tab Discard? Only active tabs will be loaded, so you can have thousands upon thousands of tabs without any impact on memory usage or performance.

I use Auto Tab Discard [0], which offloads tabs after a period of time. They still show as normal tabs (with a "ZZZ" icon to indicate it's been discarded), and the website reloads when I switch to them.

When I open the browser after closing it, the session is restored with all but the current tab offloaded so it opens quickly and using very little resources.

My current session has tens of tabs, only a handful of them active. It uses about .5% CPU when idle, and less than 1Gb RAM.

[0] https://add0n.com/tab-discard.html

Also https://github.com/rNeomy/auto-tab-discard, which despite the name, doesn’t close tabs, it just unloads them from memory.

I'm using Auto Tab Discard for very fine control but it is not needed most of the time. FF does this automatically now via Tab Unloading

I think there is an issue open for this in the auto tab repo. Assuming that wasn't you who opened it you can go there and give a +1 to motivate the dev.

If something like Google Chrome is using a lot of power, can I determine which sites are using the most resources in its Task Manager (Shift+Esc)? Can I use something like Auto Tab Discard to minimize resource usage in tabs I'm not using?

I think this extension does something similar: https://add0n.com/tab-discard.html

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)