#notfullylivevoidposting — Public Fediverse posts

I’ve figured it out!

options "grp:shifts_toggle,lv3:ralt_switch,lv5:caps_switch,nbsp:level3,misc:typo"

lv3:ralt_switch, misc:typo and nbsp:level3 give me a typographic keyboard. And lv5:caps_switch just gives me another button that I use as a keyboard app launcher (ISO_Level5_Shift+F → Firefox).

Sure, I can't make the tap, hold and double-tap do different things, but now I don't need #kanata (no offense).

#niri #typography #keyboard #VoidLinux #NotFullyLiveVoidPosting

I’m switching to the #NotoSans and #NotoSansMono fonts. I think I’m creating the most boring machine possible. Do you see the number of packages? 100. That includes NPM and AppImages.

Another thing I did was set up states in #waybar that hide almost everything until a certain threshold is reached. I don’t need to know if the CPU load, memory use, etc. are below 30%; “call me” when they’re higher.

I also swapped mako for #fuzzel’s relative, #fnott.

#NotFullyLiveVoidPosting #DesktopFriday

Most of the changes are hard to show. For example, since you can do “focus-column-or-monitor-left” and “move-column-left-or-to-monitor-left,” I drastically reduced the number of #niri keybindings to what I think I will actually use. I kept the logic of “Mod+” for navigation, “Mod+Ctrl+” for movement.

I also didn’t want to cover a great wallpaper: https://www.mattvince.com/product/zelda-x-ghibli-desktop-wallpaper/ There’s more! It asks for an email, but you know about “10 minute email,” right? ;)

#NotFullyLiveVoidPosting #DesktopFriday

No dealbreakers, but I think it’s important to mention that there are some problems.

No sound from the laptop’s speakers, a known bug. HDMI and audio jack work perfectly, which is what I want.

I gave up on figuring out the signals (the thing you send to a program – waybar). There are a million ways to do something, I’m fine.

Styling, ugh… That gave me more reason to keep it minimal. As I said before, besides web browsers and image editors, I avoid anything GUI now.

#NotFullyLiveVoidPosting

#fuzzel is fun! I immediately made an emoji picker:

`Mod+Period { spawn-sh "uni emoji all -f '%(emoji) %(name) %(cldr_full)' | fuzzel -d | awk '{print $1}' | wl-copy"; }`

…and clipboard manager:

`Mod+V { spawn-sh "cliphist list | fuzzel -d | cliphist decode | wl-copy"; }`

#NotFullyLiveVoidPosting

#mako is pretty simple but has a reasonable amount of configurability. You can customize how different notifications behave. For example, you can create volume and brightness sliders, place them in the middle of the screen, and make them disappear. All others would remain in the top right corner until dismissed.

#NotFullyLiveVoidPosting

Okay, #waybar… I’m not complaining, but I’m baffled by it. It’s as if someone decided #Conky was perfect, just arranging things horizontally was difficult. There are no modern niceties of any kind. Fine, now I have a multi-command script. It checks if the configuration was updated and reloads Waybar. It pulls some custom info. It even renders the clock because displaying the time as “9:30” instead of “09:30” is apparently problematic.

#NotFullyLiveVoidPosting

There is an infinite horizontal line of windows and an infinite vertical column of those lines. The navigation is simple and easy to grasp (the default bindings are perfect). Occasionally, I still move in the wrong direction, but it is very quick, so I only waste a couple of keystrokes and a little time.

Just one complaint: there is no “open or focus” command, so I made my own. As a bonus, it opens a new tab in the browser if the last item in the clipboard is a URL.

#NotFullyLiveVoidPosting

At least let me write something… As always, questions are welcome.

So, #niri. Why a window manager (compositor) instead of a desktop environment? It seems like the next logical step in choosing everything I want. I’m not going to rant about everything that’s happening in here this our neck of the software woods, but that’s feels like the only reason left to choose Linux over anything else.

And niri makes much more sense to me than tiling wm’s.

#NotFullyLiveVoidPosting

For reasons, I’ve been neglecting to write about what I’ve been doing. I’ll catch up at some point, at least with the more interesting parts. But, ignoring the “why, ” let me at least explain the “what” (you can play detective and figure out the hardware).

Unsurprisingly, this is #VoidLinux with #niri, #waybar, #mako for notifications, and #fuzzel for the app launcher. Besides browsers and graphics editors, I only have a couple of GUI programs installed.

#NotFullyLiveVoidPosting #DesktopFriday

Today, I learned about `wpa_supplicant` (that’s the default for #VoidLinux). You need to enable both that and `dhcpcd`. Then, use `wpa_cli` to add the network, SSID, and password. Enable the network and reboot, just in case. Everything seems to be working fine. It’s surprisingly straightforward.

#NotFullyLiveVoidPosting

If SSD prices were reasonable, I would just get a 256 or even 128 GB and test drive #SteamOS. My PC uses as much AMD as possible, so it fits. But in our miserable world – Nintendo logic, where you flip M to W (Morld → World), explains everything – I’m not that interested. My DIY SteamOS on top of #VoidLinux is fine ( #NotFullyLiveVoidPosting ), although somewhat finicky, and I’d rather play than tinker. Also, Valve is trying to full-on jokerfy right now, so.

Can verify that it also works with the #FlydigiVader5Pro. Need to change “idProduct” to “2401”:

KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="37d7", ATTRS{idProduct}=="2401", MODE="0666"

And look at all those additional inputs. Amazing! At half the price of the #SteamController.

#NotFullyLiveVoidPosting #SteamOS #SteamInput #Flydigi #GyroGaming

I’ve been playing more demanding games on my #VoidLinux Hack #SteamMachine. There is a way to get #Steam to recognize all the buttons and gyro of a #FlydigiApex5. Add

KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="37d7", ATTRS{idProduct}=="2501", MODE="0666"

to `/usr/lib/udev/rules.d/60-steam-input.rules`, then reboot. You need Windows to enable the feature, but then it works on Linux. Source: https://github.com/ValveSoftware/steam-for-linux/issues/12534

#NotFullyLiveVoidPosting #Flydigi #GyroGaming

I’ve been playing more demanding games on my #VoidLinux Hack #SteamMachine. There is a way to get #Steam to recognize all the buttons and gyro of a #FlydigiApex5. Add

KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="37d7", ATTRS{idProduct}=="2501", MODE="0666"

to `/usr/lib/udev/rules.d/60-steam-input.rules`, then reboot. You need Windows to enable the feature, but then it works on Linux. Source: https://github.com/ValveSoftware/steam-for-linux/issues/12534

#NotFullyLiveVoidPosting #Flydigi #GyroGaming

It also makes scheduling way simpler. Want something repeated every hour? Add a `sleep` to your script. It will do what needs to be done, wait, stop, and then `runit` will start it up again.

For more complex tasks (“do something on Sundays at 5 in the morning”, for example), swap `sleep` with `snooze`. While both `cron` and `snooze` were written by aliens who are afraid of human language, it’s easy to do a dry run of `snooze` and see if your incantation is correct.

#NotFullyLiveVoidPosting

It also makes scheduling way simpler. Want something repeated every hour? Add a `sleep` to your script. It will do what needs to be done, wait, stop, and then `runit` will start it up again.

For more complex tasks (“do something on Sundays at 5 in the morning”, for example), swap `sleep` with `snooze`. While both `cron` and `snooze` were written by aliens who are afraid of human language, it’s easy to do a dry run of `snooze` and see if your incantation is correct.

#NotFullyLiveVoidPosting

Don’t be like me and spend an embarrassing amount of time trying to figure out how to run a #runit service as a user. I guess #kanatakbd uses `cmd` to run another program (`wtype`), but permissions still interfere… 🤷 at this point I gave up.

What you *should* do is to create a user-level service: https://docs.voidlinux.org/config/services/user-services.html Then it’s simple: make a dir, put a `run` in it (`log/run` optional), and you’re done. Is it a service or a #nushell script? Both! Runit is great!

#NotFullyLiveVoidPosting

Don’t be like me and spend an embarrassing amount of time trying to figure out how to run a #runit service as a user. I guess #kanatakbd uses `cmd` to run another program (`wtype`), but permissions still interfere… 🤷 at this point I gave up.

What you *should* do is to create a user-level service: https://docs.voidlinux.org/config/services/user-services.html Then it’s simple: make a dir, put a `run` in it (`log/run` optional), and you’re done. Is it a service or a #nushell script? Both! Runit is great!

#NotFullyLiveVoidPosting

https://docs.voidlinux.org/installation/guides/fde.html

I followed this guide in a VM. It worked flawlessly, but it’s a lot! In the end, you don’t even have a user account. However, it’s a good foundation for a laptop that can leave your house. And that’s what I’m preparing this setup for. I need to test what I can simplify for myself. I also need to look into different file systems. If I’m redoing everything, it’s a good opportunity to make improvements.

#NotFullyLiveVoidPosting

https://docs.voidlinux.org/installation/guides/fde.html

I followed this guide in a VM. It worked flawlessly, but it’s a lot! In the end, you don’t even have a user account. However, it’s a good foundation for a laptop that can leave your house. And that’s what I’m preparing this setup for. I need to test what I can simplify for myself. I also need to look into different file systems. If I’m redoing everything, it’s a good opportunity to make improvements.

#NotFullyLiveVoidPosting

Copying the plugin folders manually worked. Not many of them will be useful, but I tested SteamGridDB and ProtonDB Badges.

I also tried installing a previous version of #DeckyLoader to see if it would update, but it broke. So I’ll leave it for now. I’m thinking of writing a script for automatic installation, #runit and all, which shouldn’t be hard. However, doing everything by hand is also not that difficult. As usual, feel free to ask.

#NotFullyLiveVoidPosting

Copying the plugin folders manually worked. Not many of them will be useful, but I tested SteamGridDB and ProtonDB Badges.

I also tried installing a previous version of #DeckyLoader to see if it would update, but it broke. So I’ll leave it for now. I’m thinking of writing a script for automatic installation, #runit and all, which shouldn’t be hard. However, doing everything by hand is also not that difficult. As usual, feel free to ask.

#NotFullyLiveVoidPosting

I take it back about #syncthing https://github.com/syncthing/syncthing/tree/main/etc/linux-runit Mostly: it should be simply `export SYNCTHING="/usr/bin/syncthing`.

Decided to use my old #SteamController, which made it easy. The #VoidLinux `steam-udev-rules` package is useful for this. Or does it work without it? Shrug.

I made #DeckyLoader work with #runit, but it’s store is currently unavailable (just for me?) so I can’t test it. I also don’t know how it is updated.

So, now Haiku. Still JK.

#NotFullyLiveVoidPosting

I take it back about #syncthing https://github.com/syncthing/syncthing/tree/main/etc/linux-runit Mostly: it should be simply `export SYNCTHING="/usr/bin/syncthing`.

Decided to use my old #SteamController, which made it easy. The #VoidLinux `steam-udev-rules` package is useful for this. Or does it work without it? Shrug.

I made #DeckyLoader work with #runit, but it’s store is currently unavailable (just for me?) so I can’t test it. I also don’t know how it is updated.

So, now Haiku. Still JK.

#NotFullyLiveVoidPosting

Sorta todo for later:
• gamepad (I hate `udev`);
• testing a couple of games to check if I forgot anything;
• the hardest, but not impossible part – figuring out if I can install the #DeckyLoader on #VoidLinux;
• Haiku in VM. JK.

Don’t plan on playing anything on it yet. It’s amazing how many games I’m interested in can run on much less powerful machines, including my phone. I just was in the mood for tinkering, for those few games that require a more powerful PC.

#NotFullyLiveVoidPosting

Sorta todo for later:
• gamepad (I hate `udev`);
• testing a couple of games to check if I forgot anything;
• the hardest, but not impossible part – figuring out if I can install the #DeckyLoader on #VoidLinux;
• Haiku in VM. JK.

Don’t plan on playing anything on it yet. It’s amazing how many games I’m interested in can run on much less powerful machines, including my phone. I just was in the mood for tinkering, for those few games that require a more powerful PC.

#NotFullyLiveVoidPosting

I also added a repository to #VoidLinux: just a file with one line. Really easy!

https://github.com/xJayMorex/ProtonPlus-void

#ProtonPlus is just a fancier-looking #ProtonUp.

#NotFullyLiveVoidPosting

I also added a repository to #VoidLinux: just a file with one line. Really easy!

https://github.com/xJayMorex/ProtonPlus-void

#ProtonPlus is just a fancier-looking #ProtonUp.

#NotFullyLiveVoidPosting

It was all for this…

I installed `gamescope`, `MangoHud` (case sensitive) and `MangoHud-mangoapp` (you need that one), as well as their 32-bit counterparts, just in case.

Then I ran the script from https://github.com/shahnawazshahin/steam-using-gamescope-guide Then I panicked because, while it was doing its thing with #gamescope, the screen went completely blank. But it works now and I have my own #SteamMachine already. SDDM logs in automatically, I can switch to the desktop and #MangoHud works.

#NotFullyLiveVoidPosting

It was all for this…

I installed `gamescope`, `MangoHud` (case sensitive) and `MangoHud-mangoapp` (you need that one), as well as their 32-bit counterparts, just in case.

Then I ran the script from https://github.com/shahnawazshahin/steam-using-gamescope-guide Then I panicked because, while it was doing its thing with #gamescope, the screen went completely blank. But it works now and I have my own #SteamMachine already. SDDM logs in automatically, I can switch to the desktop and #MangoHud works.

#NotFullyLiveVoidPosting

#syncthing was a hassle. I’m not sure why, as I’m dealing with multiple unfamiliar variables here – `runit` and `chpst` – but after installing `socklog` (#VoidLinux is really minimal, y’all!), I guess setting `env` before everything else was the key. In the end, my `run` file looks like this:

#!/bin/sh

exec 2>&1
exec env HOME=/home/andrew \
chpst -u andrew:andrew \
/usr/bin/syncthing serve --no-browser --logflags=0

https://github.com/syncthing/syncthing/tree/main/etc/linux-runit was not helpful.

#NotFullyLiveVoidPosting

#syncthing was a hassle. I’m not sure why, as I’m dealing with multiple unfamiliar variables here – `runit` and `chpst` – but after installing `socklog` (#VoidLinux is really minimal, y’all!), I guess setting `env` before everything else was the key. In the end, my `run` file looks like this:

#!/bin/sh

exec 2>&1
exec env HOME=/home/andrew \
chpst -u andrew:andrew \
/usr/bin/syncthing serve --no-browser --logflags=0

https://github.com/syncthing/syncthing/tree/main/etc/linux-runit was not helpful.

#NotFullyLiveVoidPosting

Hey, look who’s back!

First, #VoidLinux updated without a hitch, despite being dormant for almost a year (really?! Wow!). But I didn’t – I’d completely forgotten my sway and foot shortcuts, so I installed #KDEPlasma instead (`kde-plasma` and `kde-baseapps`). It’s graphical, I know it, I like it. Then I installed `pulseaudio` to fix the sound. Enabled SDDM. And #WezTerm, why not.

#NotFullyLiveVoidPosting

Hey, look who’s back!

First, #VoidLinux updated without a hitch, despite being dormant for almost a year (really?! Wow!). But I didn’t – I’d completely forgotten my sway and foot shortcuts, so I installed #KDEPlasma instead (`kde-plasma` and `kde-baseapps`). It’s graphical, I know it, I like it. Then I installed `pulseaudio` to fix the sound. Enabled SDDM. And #WezTerm, why not.

#NotFullyLiveVoidPosting

The demon in Asylum was so nice that I killed it twice.

By the way, I added a #NotFullyLiveSoulsPosting hashtag, similar to #NotFullyLiveVoidPosting, so feel free to filter this nonsense out.

The demon in Asylum was so nice that I killed it twice.

By the way, I added a #NotFullyLiveSoulsPosting hashtag, similar to #NotFullyLiveVoidPosting, so feel free to filter this nonsense out.

#Geekbench shows increase (85760 → 92829, ~8%) in Vulkan GPU performance from Windows 11. https://browser.geekbench.com/user/434938

Sure.

#NotFullyLiveVoidPosting

#Geekbench shows increase (85760 → 92829, ~8%) in Vulkan GPU performance from Windows 11. https://browser.geekbench.com/user/434938

Sure.

#NotFullyLiveVoidPosting

I don’t need anything fancy like volume control because I use physical knobs for that: https://mastodon.online/@alsorew/111781749957683644

#NotFullyLiveVoidPosting

I don’t need anything fancy like volume control because I use physical knobs for that: https://mastodon.online/@alsorew/111781749957683644

#NotFullyLiveVoidPosting

Everyone’s favorite thing under #Linux, setting up audio!

`sudo xbps-install pipewire`

`sudo mkdir -p /etc/pipewire/pipewire.conf.d`

`ln -s /usr/share/examples/wireplumber/10-wireplumber.conf /etc/pipewire/pipewire.conf.d/`

`ln -s /usr/share/examples/pipewire/20-pipewire-pulse.conf /etc/pipewire/pipewire.conf.d/`

`exec pipewire` → Sway’s config, reboot.

`wpctl status`

`wpctl set-default {sink ID}`

`wpctl set-volume {sink ID} 1` (not %, it goes to 1)

😰 It works.

#NotFullyLiveVoidPosting

Everyone’s favorite thing under #Linux, setting up audio!

`sudo xbps-install pipewire`

`sudo mkdir -p /etc/pipewire/pipewire.conf.d`

`ln -s /usr/share/examples/wireplumber/10-wireplumber.conf /etc/pipewire/pipewire.conf.d/`

`ln -s /usr/share/examples/pipewire/20-pipewire-pulse.conf /etc/pipewire/pipewire.conf.d/`

`exec pipewire` → Sway’s config, reboot.

`wpctl status`

`wpctl set-default {sink ID}`

`wpctl set-volume {sink ID} 1` (not %, it goes to 1)

😰 It works.

#NotFullyLiveVoidPosting

Screenshot! This was a bit annoying because I wanted to have a readable naming scheme. So now it is a script that gets the name of a focused window from `swaymsg` (main pain), then creates a sub-directory and then asks `grim` to take a screenshot and output it to that sub-directory.

I know you can use `grim` to take a screenshot of a specific window, but I think that would be overkill.

#NotFullyLiveVoidPosting

Screenshot! This was a bit annoying because I wanted to have a readable naming scheme. So now it is a script that gets the name of a focused window from `swaymsg` (main pain), then creates a sub-directory and then asks `grim` to take a screenshot and output it to that sub-directory.

I know you can use `grim` to take a screenshot of a specific window, but I think that would be overkill.

#NotFullyLiveVoidPosting

Oops, broke my `fstab`: simple typo and I forgot to create a directory for the mount point. #Rescuezilla to the zilla!

BTW, one of the things I want to do with #NotFullyLiveVoidPosting is not ignore mistakes and frustrations. But I don’t want to be like “and then I spend half an hour staring at very unhelpful documentation” because it’s not that interesting, we all know that documentation is bad most of the time.

Oops, broke my `fstab`: simple typo and I forgot to create a directory for the mount point. #Rescuezilla to the zilla!

BTW, one of the things I want to do with #NotFullyLiveVoidPosting is not ignore mistakes and frustrations. But I don’t want to be like “and then I spend half an hour staring at very unhelpful documentation” because it’s not that interesting, we all know that documentation is bad most of the time.

Instead of installing a browser, I just downloaded an AppImage of Ungoogled Chromium. https://ungoogled-software.github.io/ungoogled-chromium-binaries/ It just needed the `nss` package (AFAIK there’s no easy way to find that out, just to look up the library it yells about).

Then I made my own KDE Connect. Well, not really: it’s just a couple of commands that save and load the clipboard (with `wl-clipboard`) into a file that is synced with Syncthing. Good enough for a minimalist setup I’m trying to achieve.

#NotFullyLiveVoidPosting

#Xfce flavor of #VoidLinux live image boots from #Ventoy fine. Peculiar.

#NotFullyLiveVoidPosting

I fell into another hole. You see, there is no #OhMyPosh in #VoidLinux, only #StarshipPrompt. So I thought about it… And now I have styled my prompt in #Nushell itself, no other stuff necessary.

It doesn’t do anything fancy, just picks colors based on hostname and also shows status of a git directory. So 100% the same as my Oh My Posh config.

#NotFullyLiveVoidPosting

Ok, I’m done for today, not sure when I’ll be in the mood to continue (it’s for fun first and foremost!). Tomorrow? Shrug. But here is a joke for you:

How minimalist is #VoidLinux? If you install a web browser, the number of packages doubles!

#NotFullyLiveVoidPosting

`sudo micro /etc/default/libc-locales`

Uncomment some stuff.

`sudo xbps-reconfigure glibc-locales --force`

`sudo micro /etc/locale.conf`

Add/Change `LC_TIME=`. Reboot.

That way I can have English language for text and everything, but not have to stare at that AM/PM nonsense.

I am also very curious about the `xbps-reconfigure`. Seems like a very good idea for fixing problems, but that’s theoretical at this point.

#NotFullyLiveVoidPosting

`wmenu` just works.

`clipman` https://wiki.archlinux.org/title/Sway#Clipboard Not sure about that command, but clipboard works without it. Maybe it is for history and stuff?

Also, that’s your autostart: just `exec [command]` (`exec syncthing --no-browser`). Very simple. Pretty cool.

#NotFullyLiveVoidPosting

`sudo xbps-install wmenu clipman font-adobe-source-code-pro gdu btop micro fastfetch nushell syncthing`

`mkdir ~/.config/foot/`

`cp /etc/xdg/foot/foot.ini ~/.config/foot/foot.ini`

`micro ~/.config/foot/foot.ini`

Default shell: `shell=/usr/bin/nu`. It is possible to set #nushell as the login shell, but I would say it is unnecessary and on Void would require adding environment variables to `$nu.env-path` (https://github.com/nushell/nushell/issues/7941), which is annoying.

#NotFullyLiveVoidPosting

I don’t write everything I do, but I have reinstalled it a few times to try some things. The goal is to poke at it, you know :)

For example, I’m now on a version with a swap partition. I know there is a debate, and I don’t know enough to care one way or the other.

#NotFullyLiveVoidPosting

`sudo xbps-install -Su`

`sudo xbps-install dbus-elogind elogind polkit mesa-dri sway foot xorg-fonts`

`sudo ln -s /etc/sv/dbus /var/service/`

`sudo ln -s /etc/sv/polkitd /var/service/`

`sudo reboot`

Login, `sway`

The minimalist #Sway installation is done.

#NotFullyLiveVoidPosting

Aside: Logitech K240 is not a particularly comfortable combo, but it is a keyboard and a mouse that work with a dongle, no need for Bluetooth, which is not there yet, and is quite small, so it is convenient backup to have. Case in point: me doing this.

#NotFullyLiveVoidPosting

Although this is clearly a UEFI system, I had to create an MBR with only one partition (no swap) to install. Otherwise I would get GRUB errors no matter what partitioning scheme I tried. 🤷

#NotFullyLiveVoidPosting

#VoidLinux refused to boot from #Ventoy. I dd’d it.

Feel free to block the hashtag if you don’t want to see more post of me kinda live (but turn-based) tinkering with Void on a real hardware.

#NotFullyLiveVoidPosting