This was cool but there were a few issues such as me not being able to
find the infamous "dock patch" despite grepping for dock on
https://dwm.suckless.org/patches/, which resulted in the keyboard hiding
tiled windows and being below floating windows.
There was also an issue where starting corekeyboard from dwm would
result in styling not being applied compared to starting it from the
terminal.
A third issue was that from a quick attempt I couldn't get callaudiod to
start inside dwm, which was required for gnome-calls.
Overall it looks like I will be using Phosh until further notice on the
PinePhone, as I've already gotten it to work well enough for my use case.
This worked and was *significantly* faster than Phosh but resulted in a
lot of phone things broken like phone calls and the camera. Overall
quite cool to run dwm on the PinePhone but not really practical when
trying to use the PinePhone as a phone.
Note that it's possible to use an autostart patch like
https://dwm.suckless.org/patches/cool_autostart/ so startx isn't
needed although this results in dwm starting before things like
the status bar get set.
Note that glib was supposedly added for mounting-related things, but
this should be possible to upstream into the derivation instead if it
hasn't been added already.
This makes LibreWolf work well on the PinePhone without having to
manually use the FriendlyFox installation script.
Note that FriendlyFox was chosen over the mobile-config-firefox script
from postmarketOS due to FriendlyFox having less issues overall, such as
not breaking when the right click menu is long and popup menus having
altered styles for mobile support.
Might add some more search engines later, but Mullvad usually produces
better results for less popular content, especially with topics such as
PinePhone troubleshooting.
I don't use deno enough to justify having separate abbreviations for it,
and I doubt I will anytime soon due to the vastly superior ecosystem of
npm. Just as an example, `deno task` autocomplete support isn't
implemented, whereas `npm run` does have autocomplete.
I only use alacritty on the phone due to the superior touch support.
Touch support might be added to kitty later if someone is willing to
patch it. See: https://github.com/kovidgoyal/kitty/issues/5432
Now that tmux works again, it makes sense to choose it over zellij due
to the vastly superior community support around it. Using tmux-256color
makes colors work properly in programs like htop, and neovim benefits
from squiggly lines and italics from kitty as well.
Not interested in dealing with fixing the nixf-tidy issue here which
would cause a massive formatting diff with nixfmt-rfc-style. Might
upstream later or find a better solution without chameleon.nvim.
