This was my attempt at using yambar in both Xorg and Wayland with the
anybar dwm patch however starting yambar resulted in the session being
unresponsive until yambar was killed from another tty.
Avizo had some issues that ultimately made me return to the old and
reliable dunst. For example, the home-manager service would fail to
restart after the computer was idle for a set amount of time.
The way avizo manages its window also resulted in compositors like
Hyprland and picom showing a blur artifact when avizo tried to fade
itself. Ultimately using dunst simplifies things and avoids having
to look in two different places for notifications.
mpdris2 seems to have much greater feature support than mpdris2-rs,
notably the inclusion of lower notification urgency by default and the
ability to start mpdris2 without it showing a stopped notification.
The biggest feature, however, is the possibility to run multiple
mpdris2 instances at the same time. This was impossible to achieve
with mpdris2-rs since it would claim that the bus was already taken.
Notably this enables much smoother usage when running mpdris2 in both
Hyprland and dwm at the same time. Combined with dunst, this enables
seamless notifications between the two environments.
Avizo seemingly has better support than swayosd in dwm, so this change
makes the OSD consistent across both environments.
Long-term it may be useful to figure out why swayosd would tile under
dwm and whether or not it'd be possible to fix upstream.
I never use kitty diff and it doesn't seem to work in Hyprland anyway
due to the following error:
> [0.215] [glfw error 65544]: process_desktop_settings:
> failed with error: [org.freedesktop.DBus.Error.UnknownMethod]
> No such interface “org.freedesktop.portal.Settings”
> on object at path /org/freedesktop/portal/desktop
Fixes an issue where New Tab Identity wasn't being loaded on first
launch of the profile due to settings not being profile-specific.
Long-term this also makes it possible to take advantage of the "Show
only modified preferences" feature, which showed our changes as the
defaults before.
This seems to work, which is great.
For some reason it wasn't being initialized properly inside the virtual
machine but it does work on actual devices.
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.
