This used to be a separate script in my ~/.local/bin, however the script
is short enough that it doesn't need to be a separate file, and I don't
use it outside of the shell anyway.
This is version 0.4.9 and should work out of the box without any
modifications. Note that the mpv config must be edited to support
this script, which I'll add in the next commit.
In the future it may be nice to automatically add a selection of
backgrounds that can be rotated through, or support getting those
images from an external source.
Currently this script works by getting the total play time of the
playlist when pressing F12. Time will tell if I decide to improve upon
it later, although it already does a good job at what it's supposed to
do.
Although alacritty is an amazing terminal emulator, I am not interested
in maintaining configuration files for it at this time.
The current config works and is an excellent replica of the current
kitty config. If you have a desire to use alacritty, you can use the
files in this commit to get amazing support for things like pywal.
The reason alacritty is being removed is because it doesn't fully
support fcitx. Currently "inline input" doesn't work in Xorg, and it's
impossible to see input under GNOME Wayland.
For simplicity, only the terminal emulator that works the best for me
will be officially supported, since I've never had a reason to use
alacritty anyway.
Source: https://github.com/alacritty/alacritty/issues/1613
This likely fixes an issue I had earlier, although I don't remember what
it was. In any case, this change is a positive one since toggling the
bar is now instantaneous as well.
Although recoloring documents is great for rice screenshots, most of the
time we want to see a pdf in its original form before deciding to
recolor it. Most of the time recolors occur when a "dark mode" is
necessary, which zathura does a good job with.
Previously ale would show an error message when dealing with JavaScript
files without an .eslintrc. That has now been fixed and standardjs works
as intended.
This is no longer needed since I plan to focus fully on bspwm instead.
Note that I may still use GNOME on multi-monitor setups and other
devices where having the convenience of bspwm and sxhkd isn't necessary.
Since I've decided to ditch sway, I no longer have to deal with waybar
either, which is nice. Although waybar is nice-looking, there isn't much
of a difference between it and polybar in day-to-day usage, and other
factors such as ease of maintenance are far more important.
Although using a Wayland window manager was cute, Sway always felt like
a gimped version of bspwm to me. This is likely due to many of the bspwm
features I use, as well as certain X applications not working well under
Wayland (such as feh).
I am also not interested in maintaining the config for Sway, and prefer
bspwm's approach where it's configured through bspc and shell scripting.
In summary, "after all these years", Sway is still more trouble than
it's worth for me personally, and I'd rather invest that time focusing
on my existing bspwm setup, which has always been pleasant to use.
Similar to bspwm, all keybinds are now handled with super to avoid
conflicts with other applications. In the future it may be useful to
replicate the rest of the bspwm environment under sway.
