This signposts that we've actually moved permanently (fingers crossed)
to Sway. I should have done this the moment the first
non-backward-compatible change went in so I could revert to that point,
but meh.
This is a rough one. Waynergy is the Wayland-compatible replacement for
synergy. As far as I can tell it works largely on black magic.
For whatever reason, Waynergy doesn't handle keycodes the same way
Synergy/Barrier do. It uses raw codes as sent by the server. These codes
can exceed the X cap of 318, resulting in keys being ignored in XWayland
sessions.
The dev's recommended path to keyboard support is to use a custom xkb
keymap and I guess just shrug at the dropped keys over 318. My method
uses the stock evdev xkb keymap and instead uses raw keycodes to swap
out-of-band keys to their expected keycodes.
The warning the dev gives is this is brittle and won't work on any other
OS, or possibly keyboard/box. I don't care.
This may not be a backward compatible change, hopefully it won't matter.
We add the directive to handle floating windows via app_id as well as
window class, since Wayland doesn't use window classes, and we add a
directive to let Sway turn off mouse acceleration.
We make the X Class match `__user_requests_float` a wildcard match so it
can begin with anything and make mpv launch with the class
`mpv__user_requests_float`. Then we make that class `no_focus` in i3.
This should prevent focus from jumping to mpv if any of my weird video
playing automation scripts launched mpv suddenly.
This just generates a simple list for sharing a todo list with people.
Also remove the news prompt hack. Apparently taskwarrior does an ==
check for the flagged version and not >. Just it only bothers you every
few runs so I thought it worked but it didn't.
Newest Qute has a crash bug if you don't cull QT service workers on
startup. This used to be a Windows thing but now it's on Linux I guess,
so let's just make it the default.
This doesn't allow more simultaneous notifications. It just sacrifices
some RAM to store more notifications in history, which is important if I
want to be able to call and review history.
Noticed rofi wasn't handling selection highlights properly any more. In
troubleshooting found the stylesheet was massively over-complicated
since it was a copy of a less simple stylesheet in its origins.
Simplified and fixed the bug.
Auto-init tab completion in ZSH
Normalize backspace handling in vim (for windows support)
Force dunst to place notifications on monitor 1, since I moved to
two-monitor setup.
- Add Xft Xresources to make fonts not ugly
- Add dunstrc now that I'm using dunst
- Manage GTK settings now that I'm free of mate-settings
- Add an i3 keybind for pcmanfm
- Make kitty font size chords +/- by 1pt and not 2pt
- Explicitly specify fonts everywhere
- Put barrier and dunst in xinitrc
- Make QT theme explicit via env var
- Move ZSH keybinds to global since Arch doesn't bind them
- Switch to a base16 builder wrapper I wrote myself
- Switch small details on a bunch of templates
- Switch to a QVP based color scheme I wrote myself
This should form the most rational default for colors going forward.
