sxhkd | picom | |
---|---|---|
42 | 109 | |
2,673 | 3,815 | |
- | - | |
0.0 | 9.7 | |
8 months ago | 12 days ago | |
C | C | |
BSD 2-clause "Simplified" License | 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.
sxhkd
-
How handle two speakers in dwm?
Hello, firstly I would separate all these non wm related keybindings to a program like sxhkd (https://github.com/baskerville/sxhkd) it's config is easier to modify on the fly and less bloat/unrelated stuff in window managers codebase is always better.
-
whkd: A simple hotkey daemon for Windows
After getting frustrated trying to update the library generation code to conform to the AHK2 syntax changes, I decided to run with an idea that I've had for a while now: writing my own simple hotkey daemon for windows based on skhd and sxhkd.
- How to make a keybinding for dmenu_run in .xinitrc?
-
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.
-
shod: an acme-like window manager that tile windows inside floating containers
You control shod via a remote controller, called shodc. You map shodc calls to keybindings using a third application (a keybinder like sxhkd).
-
Chromebook
That said, if you enable linux app support, you can use something like sxhkd for hotkey definitions in combination with bash scripting.
-
Volume Control Works on MATE but not BSPWM
Not that I know, at least the general syntax is said to work with KEYSYMs only. However! I've been reading some more about it and you can try this: if you're not using a US layout keyboard, start sxhkd -m 1 as described here https://github.com/baskerville/sxhkd/issues/249. And just out of curiosity, maybe you can check if you have the proper drivers installed (again, sorry I don't know the details) but at least I have xf86-input-libinput installed.
-
Getting keyboard to work....
Because we specify super/ctrl/alt as modifiers x11 doesn't distinguish between left and right. See https://github.com/baskerville/sxhkd/issues/89
-
Best way to insert the ñ character.
Now I have an script that copy the char to the clipboard when I press that shortcut. This is archived using [sxhkd](https://github.com/baskerville/sxhkd). Is there a better way?
-
Show HN: A tiling window manager like i3wm written in C#
komorebi dev here. I can't tell you the number of times I've wanted to just write my own take on sxhkd[1] for Windows and use that to manage my own keybindings for komorebi instead of ahk.
You can just as easily write your own/use another hotkey daemon or PowerShell scripts to handle komorebi's configuration and keybindings, in that sense there is no dependency on ahk at all. However, the inertia around ahk in the Windows ecosystem is undeniable and it's in the interests of making adoption and onboarding easier that the project provides example ahk files and has invested in an ahk code generation library.
My thoughts on the dominant hotkey daemon in the Windows ecosystem aside, I remain convinced that the famous bspwm socket communication architecture[2] is the best way to handle both configuration and keybindings for a tiling window manager that has been proposed to this today.
Unfortunately I have to concede that there is a certain configuration burden that comes with komorebi, which is amplified in some cases by having to write/maintain ahk. This configuration burden is largely due to the highly fragmented nature of Windows application development that is discussed often on HN and it is inescapable.
With this in mind, the next release of komorebi (currently available on master) will invest even more heavily in automatic configuration generation.
A separate repository of common application-specific configuration tweaks[3] (in YAML!) has been created which I and others from the komorebi Discord server are contributing to, with the goal of having the edge cases for as many applications as possible fully documented so that a comprehensive configuration file can be generated[4] for the user which ensures that every (major) Windows application behaves as expected under a tiling window manager.
I hope that other Windows tiling window manager developers can use these YAML definitions in the future to handle the same edge cases in their projects so that eventually there will be a tiling window manager of every flavour (bspwm, i3wm etc.) available for Windows users where having to manually accommodate and compensate for the non-standard behaviour of individual applications is a thing of the past.
[1]: https://github.com/baskerville/sxhkd
[2]: https://github.com/baskerville/bspwm#description
[3]: https://github.com/LGUG2Z/komorebi-application-specific-conf...
[4]: https://github.com/LGUG2Z/komorebi/#generating-common-applic...
picom
-
Can't find picom and polybar default config files
(https://github.com/yshui/picom/blob/next/picom.sample.conf)
- ArchLinux sluggish on 4K monitor
-
[photo] installing Debian :)
Also I took a census and zero founding members of NWA are "straight outta Picom". That's right, you heard it here first: Not even MC Ren is running Picom.
-
FPS drops when scrolling in monocle layout with Picom
Update: after reporting in picom GitHub repo this is temporarily solved by using --no-frame-pacing. Looks like a recent commit causes this. You can view the discussion here: https://github.com/yshui/picom/issues/1072
- Zoom in and zoom out in dwm?
-
Compositor Options for Animations
NEED HELP TESTING (write your issues here): https://github.com/yshui/picom/issues/1052
-
[dwm] Beginning on linux desktop, first ricing
Compositor : picom
-
In Picom with the rounded-corners setting how do you apply alpha to the menu list?
It looks like this was identified and the repo corrected in Jan (https://github.com/yshui/picom/issues/808) but the NixOS package has not been updated since Nov.
-
I have two Linux computers which I use for gaming.... somehow the one with slightly inferior hardware gets significantly better performance. I'm trying to figure out why... any ideas?
If you have compositing you are likely using picom. You can check if it's running with ps -A | grep picom. I've never dealt with this issue as I don't really game on linux often, but I'm sure there's a solution somewhere in the github docs or issues. Worst case scenario you could always just kill the process with killall picom whenever you're about to game, and re-enable it with picom -b after. Do note though that currently running windows might bug out a bit when you kill/start the compositor.
-
What are WSL limitations compared with a pure linux install?
Picom is broken for me with GLX backend related Github issue.
What are some alternatives?
xcape - Linux utility to configure modifier keys to act as other keys when pressed and released on their own.
compton - A lightweight compositor for X11 [Moved to: https://github.com/yshui/picom]
scripts - *Well documented* scripts exploiting some useful UNIX utilities.
compton - A compositor for X11.
bspwm - A tiling window manager based on binary space partitioning
picom - A lightweight compositor for X11 (previously a compton fork)
releases
wayward - Fast desktop shell for wayland and weston.
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
sway - i3-compatible Wayland compositor
shotkey - A simple and lightweight hotkey daemon for X with configurable custom modes and key chords (in ~200 LOC)
void-packages - The Void source packages collection