patches
xdotool
Our great sponsors
patches | xdotool | |
---|---|---|
94 | 38 | |
268 | 2,981 | |
- | - | |
5.9 | 4.1 | |
16 days ago | about 1 month ago | |
C | ||
- | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
patches
-
alpha patch makes my dwm doesn't starting
It's difficult to make alpha and systray patches sing together. Use bakkeby patch that does them both: https://github.com/bakkeby/patches/blob/master/dwm/dwm-alpha-systray-6.3_full.diff
-
Layout rule for a program
I think the easiest solution here would be to incorporate all attach patches (for example via attachdirection or attachx) then have a client rule option that determines how the client should initially attach; as the master, first in the stack, at the bottom or above or below the currently focused window.
So far I found https://github.com/bakkeby/patches/wiki/monitorrules, but it works per monitor/per tag, but I want it to work per program like the default rules, except extended
-
How Do You Setup Workspaces Properly?
I am trying to setup my workspaces for stumpwm, but am running into a wall due to not being able to find much documentation, is there is even support, for a few things I want to do. For some background, I am coming from dwm which I have used for a few years and even forked a few times. In dwm I had a rather simple, but extremely useful, setup where I would store specific types of programs on specific tags. I was able to figure out getting this done in stumpwm and it working just fine. The main issue with this portion of my workspace setup is that the Default workspace still exists. I have tried to figure out how to delete it, but cannot. I know how to rename it, so I could just do that and use it for my terminals, but the issue arises where I have no idea how to change it from the default stacking layout to the dynamic one. Any advice? Additionally, is there a way to get something like dwm's fakefullscreen?
-
dwm-flexipatch: statuscmd integration in dwmblocks
I would like to add the statuscmd (for dwmblocks) feature to my dwm build. I tried this patch (from the suckless website) and this one, from u/bakkeby's Github, which seems more pertinent to my case since I use dwmblocks. I also patched my dwmblocks build with this patch, from the suckless website.
-
automatic drag(c,m)fact in resizemouse
dragcfact is a patch that depends on another patch, cfacts, that assigns a 'weight' to each client in the view area and allows you to resize them by increasing or decreasing the weight of a given client. Yes, in the case of the tile layout that does allow for 'vertical' resizing.
-
[dwm] Vanitygasp per tag?
Another way you could achieve this is via floatpos. One way I use this is to toggle tiled windows to become floating and take up 80% of the screen, which gives a kind of semi-fullscreen mode which is kind of nice.
-
bspwm Swallow
I don't know what they are refering to, but the swallowing that has become popularized is not what that screenshot shows. The functionality is taken from Plan9's window manager, rio. When you launch, say, firefox from a terminal on non-swallowing window managers the terminal just sits there and the window is spawned on it's own. With swallowing, the terminal swallows the window in that the newly spawn windows takes up the window that is the terminal until it exists at which point the terminal window is restored. I can not an example of this in video, but there are patches to implement this into dwm such as rio draw/swallow
- Any alternatives to Wallpaper engine on Linux?
xdotool
-
AMD Ryzen 7 7800X3D: Windows 11 vs. Ubuntu 23.04 Linux Performance
Maybe not AHK exactly, but it essentially does the same: xdotool
-
gtk-rs: can't get window ID with command inside connect_show or connect_realize
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):
-
My (challenging) experience building a window switcher for Ubuntu
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.
-
Focusing/switching X11 windows with a Rust crate
Right now, I'm focusing (switching) X11 windows with a shell command (xdotool) from inside my Rust program:
-
X Window System Basics
Maybe xdotool [0] is what you're looking for.
-
Ask HN: What's Your Proudest Hack?
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!
-
How to use fzf as file picker in browsers?
If you don't want to do that, if you use Xorg, perhaps xdotool can help you.
-
What's the closest equivalent of AHK for LINUX?
For GUI automation and the like, I would recommend checking out xdotool and maybe sxhkd for keybinds -- though, each DE/WM tends to have some method of handling keybindings in its own way.
- Show HN: AutoHotkey for Linux
-
What software do you miss from Windows & macOS?
For stuff like that where you don't need to read window properties, I would use xdotool: https://github.com/jordansissel/xdotool
What are some alternatives?
dwm-flexipatch - A dwm build with preprocessor directives to decide which patches to include during build time
ydotool - Generic command-line automation tool (no X!)
AutoKey - AutoKey, a desktop automation utility for Linux and X11.
wtype - xdotool type for wayland
archweb - Arch Linux website code
chadwm - Making dwm as beautiful as possible!
dwm-single-tagset-6.2 - single-tagset patch for dwm 6.2
dwm-directionalfocus - Adding directional focus to dwm
keepassxc - KeePassXC is a cross-platform community-driven port of the Windows application “Keepass Password Safe”.
i3-vim-focus - Vim plugin for seamless navigation between i3 and vim
rofi - A huge collection of Rofi based custom Applets, Launchers & Powermenus.
us.zoom.Zoom