One version of waynergy made a bad assumption about mousewheel speed if
you're using the wl-roots method of input handling and would set the
multiplier to 8, causing the mousewheel to send things spinning out of
contorl. That's been fixed but there's no harm in declaring this
explicitly anyway.
I apparently forgot to do this ever. I've been using this for about two
months now.
I just reused the modules I built for my swaybar, which already output
close to the proper format; now I just call the modules directly with `if
__name__` hooks to output Waybar format instead of Swaybar format.
This has been a giant mess but I have a solution now.
Primary font: Bitstream Vera
Primary monospace font: Hack
Then I have Nerd Font Symbols (2048 em non-mono) for powerline,
fontawesome, etc glyphs. Non-mono because mono shrinks the glyphs
vertically an unreasonable amount. Same reason I'm not using the
nerd-font patched ttf-hack.
I have to use Hack over Bitstream Vera Sans mono because Bitstream
specifies a few glyphs used in powerline and they're not shaped right,
for example the triangular ends of banners. Hack fixes this.
Then there's the complete Google Noto set. Noto is "Everything" when
installed with the noto-fonts, CJK, and Emoji. You have to explicitly
declare wanting the color emoji or you get the black and white stuff.
Noto provides a few misc glyphs that Hack and Nerd Font Symbols both
don't, like heavy check and heavy ballot x which are used in my shell
prompt.
With noto-fonts installed and my userland fontconfig using prepends for
the fonts I want, the entire giant Noto set falls in as a fallback
behind it all without needing to be defined.
This sucked to suss out; trying to avoid Google stuff made it 100x more
complicated and I just kind of gave up.
We set up a fonts.conf to specify Bitstream Vera for all my font
preferences with a fallback to the Noto Color Emoji. This should
standardize font/emoji support and my method falls back to system
fontconfig if these aren't font.
Then we swap alacritty and sway to monospace.
I dropped ttf-terminus out of my loadout and sway broke. I prefer
standardizing on DSM at this point anyway.
Also remove a vestigal sway config directive.
- Drop the audio normalization filter for mpv. It was doing more harm
than good.
- Make the tab bar in qute only display if I have multiple tabs
- Kill mouse interference in vim dead
We drop mpv on the TV being fullscreen in favor of having no borders.
This makes it look full screen while allowing multiple feeds if needs
be. We also remove the swaybar from the TV so it doesn't chew up space.
- Configure sway to place displays matching reality
- Reconfigure sway mpv shortcut to use regular clipboard, not primary
- Drop the hard placement of dunst's output so it uses display 0
This just adds `--image-display-duration=inf` so if I grab a URL and
open it in mpv with Sway's hotkey, it doesn't blink on for a few frames
then exit.
This just drops i3-nagbar for swaynag, changes i3-msg to swaymsg, and
mentions of i3 to sway. The former even worked fine, just did weird
things with windowing.
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.
