Note that although it's possible to make fcitx work with alacritty as
well, the current implementation doesn't show what you're typing as
you're typing it, which is inconvenient.
Because of this, I recommend using kitty in all cases if switching input
methods is important for your use case. kitty also has the advantage of
image preview support on both xorg and wayland, since ueberzug does not
have wayland support.
Note that I previously set up a working environment with ibus-mozc
which, although was cool (and better than ibus-anthy), did not offer all
the benefits that fcitx provides. Now that I figured out how to make
fcitx work on both xorg and wayland, as well as in applications like
anki, this is my preferred input method for personal systems.
The default mpv settings use traditional rendering methods in order to
support older hardware. Since we're running on modern hardware, we can
take advantage of the higher quality settings that mpv offers.
This is similar to bspwm, except new workspaces aren't automatically
created and empty workspaces are skipped.
Although creating a script to handle this should be possible, sway
doesn't offer any real benefits to me since bspwm does everything that
sway can do with the addition of input method, image preview, and other
features being better supported on xorg.
To reiterate, I like the idea behind sway, however I am more fluent with
bspwm and xorg and prefer how windows are managed in bspwm. For software
that only works on wayland, sway is a lightweight alternative to
committing to a full-featured desktop environment like GNOME.
Since the device we're using is normal DPI, we have to manually adjust
these two values. Note that the rest of the setup is mostly automated
when it comes to determining the size of things.
We actually still need compton (now picom) for screen tearing in bspwm,
so we'll add it back now. In the future it may be useful to keep
dotfiles in the repository even when I no longer use them, since the
configuration itself may still be useful.
So far my experience with LunarVim has been positive. Although there are
some gotchas and your own configuration may be better in some cases, the
defaults used are pretty nice and should enable developers to get up and
going quickly with neovim.
I like how sway handles workspaces. This change makes it so bspwm uses
numbers as the workspaces and polybar only shows workspaces that are
being used in the bar.
