I'm not sure what other changes would be in your sightlines given that you were happy with Ubuntu, but I usually go to the Arch wiki in those times to see what fat I can trim off of my setup.
I'm not sure what other changes would be in your sightlines given that you were happy with Ubuntu, but I usually go to the Arch wiki in those times to see what fat I can trim off of my setup.
It comes with sensible default for a good i3 experience but you keep the Ubuntu "universality".
The good stuff from Ubuntu-gnome (easy-to-use common settings GUIs, utilities etc), + the good stuff from i3, well put together and simple to customize, i3-gaps by default, and easy to install.
It also led me to discover i3blocks/i3xrocks which I didn't know I needed.
here's an example of a i3xrocks script for bluetooth status in the tray.
#!/bin/bash
# how hard is it to find a bluetooth symbol in common fonts...
# more icons at https://fontawesome.com/cheatsheet?from=io
LABEL_ICON= #ᛒ # '' # # # ᛒ
LABEL_FONT="Material Design Icons"
LABEL_COLOR=${label_color:-$(xrescat i3xrocks.label.color "#7B8394")}
VALUE_COLOR=${color:-$(xrescat i3xrocks.value.color)}
VALUE_FONT=${font:-$(xrescat i3xrocks.value.font)}
PANGO_START="<span color=\"${LABEL_COLOR}\" font_desc=\"${LABEL_FONT}\">${LABEL_ICON}</span><span color=\"${VALUE_COLOR}\" font_desc=\"${VALUE_FONT}\">"
PANGO_END="</span>"
NCONNECTED=$(expr $(hcitool con | wc -l) - 1)
echo ${PANGO_START}${NCONNECTED}${PANGO_END}
if [ ! -z "$button" ]; then
/usr/bin/i3-msg -q exec /usr/bin/gnome-control-center bluetooth
fiAny pointers for an i3 user moving to Regolith?
So could you clarify for me, what's the relation between being a "tiling windows manager" and being light? Is it that for some technical reason one would expect tiling windows managers in general to be lighter than non-tiling? Or is it that orthogonally to the tiling aspect, i3 specifically aims to be light?
My non-expert take on this is that the sort of person who sees value in the efficiencies from using a tiling WM are also of a kind to use system resources efficiently too, even though they are orthogonal characteristics.
* space splitting for launcher * some sticky displays in multi-display desktops
There is also https://swaywm.org/ if someone thinks they should run wayland.