picom VS void-packages

(https://github.com/yshui/picom/blob/next/picom.sample.conf)

Also I took a census and zero founding members of NWA are "straight outta Picom". That's right, you heard it here first: Not even MC Ren is running Picom.

Update: after reporting in picom GitHub repo this is temporarily solved by using --no-frame-pacing. Looks like a recent commit causes this. You can view the discussion here: https://github.com/yshui/picom/issues/1072

NEED HELP TESTING (write your issues here): https://github.com/yshui/picom/issues/1052

Compositor : picom

It looks like this was identified and the repo corrected in Jan (https://github.com/yshui/picom/issues/808) but the NixOS package has not been updated since Nov.

If you have compositing you are likely using picom. You can check if it's running with ps -A | grep picom. I've never dealt with this issue as I don't really game on linux often, but I'm sure there's a solution somewhere in the github docs or issues. Worst case scenario you could always just kill the process with killall picom whenever you're about to game, and re-enable it with picom -b after. Do note though that currently running windows might bug out a bit when you kill/start the compositor.

Picom is broken for me with GLX backend related Github issue.

I was looking for a lightweight OS to run on old Asus Eee PC 1005 HA, which uses a 32-bit Intel Atom N270 processor. I installed Void Linux (https://voidlinux.org/).

I may give DSL 2024 a try and see how it compares.

Linux Void

My computer is running Void Linux and it has only a wired network connection. I can hook up my phone for USB tethering if I need to connect to the WiFi of the ESP32. How do I update the software without downloading some shady programs from filesharing site links on my system? I have the Arduino IDE and the esptool.py script installed.

Classic "everyone is using the software wrong, but it's the fault of everyone, and not the software".

Some distros like Void seem to patch this out.[1]

From mandoc/mdocml's mandoc_char(7) [2]

In roff(7) documents, the minus sign is normally written as ‘\-’. In manual pages, some style guides recommend to also use ‘\-’ if an ASCII 0x2d “hyphen-minus” output glyph that can be copied and pasted is desired in output modes supporting it, for example in -T utf8 and -T html. But currently, no practically relevant manual page formatter requires that subtlety, so in manual pages, it is sufficient to write plain ‘-’ to represent hyphen, minus, and hyphen-minus.

Which is the common-sense thing to do.

Meanwhile, GNU projects become increasingly less relevant due to obnoxiousness like this.

In general the amount of wankery of "the correct hyphen" is staggering.

[1]: https://man.openbsd.org/mandoc_char

[2]: https://github.com/void-linux/void-packages/blob/20c66829134...

So I was about to configure a new Archlinux build on my PC and came across Void Linux. I had already read about it a year ago but never researched it in depth. I know that is a Linux distribution made from scratch, with a different package manager and so on. Void Linux users or people who have tried it, what are your thoughts on it? Do you think the PM is easy to use? what about updates and bugs? what desktop or Tilling Window Manager do you use? could you tell me about it?

Good news about dbus-next: https://github.com/void-linux/void-packages/pull/46760