Ok, this is confusing...

When I run #NeoVim from any terminal, it has a white background, just like my terminal.

When I run neovim from a terminal started by launcher like #rofi or #fuzzel, it has a gray background.

This is both in #Debian linux + #Swaywm and #OpenBSD + #i3wm.

So confuzzled.

#viernesdeescritorio #i3wm #xfce
loc-os bzzz

I came across something recently that basically stressed the importance of understanding the tools you use on a daily basis to get the most out of them. It suggested that you need to get familiar with the primary sources of docs as well and not just distilled summaries that hold your hand and give you a generic solution to one particular problem your trying to solve. With that in mind, my reading list lately has been the official docs for #neomutt, #irssi, #i3wm, #opnsense, #tmux. I think this is more important than ever when it's so easy to use an #llm to search for information.

Something I miss from #Tiling wms/compositors like #i3wm and #sway when I'm on #KDE:

I use #Yakuake on KDE #Plasma to have a terminal that's easily accessible, but stays out of my way when I don't want to see it.

On tiling setups, I use disappearing windows (I forget the actual name of the feature) that will pop up when I hit super+-, appear one at a time, and then disappear.

Yakuake lets you do tiling as well within its window, but I kinda miss the ability to cycle through a bunch of windows very easily. I mean, I've got the keyboard shortcuts set up very nicely, so it's just F12 to make the window appear and disappear, and then control+tab to cycle through tabs or control+pgup/pgdown to jump between panes, but somehow the tiling setup is just a bit easier to do. Less thinking, just super+-. ;)

I don't know if I'll continue to use tiling setup too much longer, though. It's too aggravating to figure out how to get the occasional gnome program to work properly. There's always some kind of fancy library initialization that I fail to get right. It's easier to just use a DE and whittle it down to nearly tiling levels of productivity.

The way I work in 2025. A fun tour through my workstation setup: i3, Firefox, Emacs and shortcuts galore. Theming and translucency. Automated daily routine, including networking, VPN setup, backups and agenda files. Oh, and I use Arch, btw.

https://skybert.net/dongxi/the-way-i-work-in-2025/

I use #i3wm inside #KDE session. For some time I'm unable to log out. Here's the bug report: https://bugs.kde.org/show_bug.cgi?id=488277

There is a workaround: https://github.com/DMaroo/fakwin

And here's my package for #openSUSE: https://build.opensuse.org/package/show/home:etamPL/fakwin

How to change keyboard layout in i3 window manager
https://youtu.be/MSwr9gyz4V0

My desktop usually involves my cat, especially in the early morning.

#ShowYourDesktop #KeyboardCat
#CatOfMastodon
#i3wm

Been tweaking my #Rofi theme, because it was rainy and I was too knackered to do anything else useful today. Rofi is an application switcher and more (calculator, character picker, launcher, weather widget, etc.). It is used in minimalist window managers like #i3wm, instead of a top-bar, dock or Start™ menu.
I used to use #Litestep on Windows, and using i3 and Rofi to DIY my own graphical shell feels similar.
#Linux #Ricing

I've been hearing a lot about niri.

As a big #i3 fan, I think #niri is the only thing that seems interesting enough for me to use it and make the #wayland switch.

This blog post sparked another wave of curiosity in me

https://ersei.net/en/blog/niri

Algun dia provaré #i3wm amb més seriositat. Millor que #bspwm . Suposo que tot és qüestió de gustos

I just discovered this gem about the #Siemens RTL tiled window system (1987)

https://open-video.org/details.php?videoid=8038

gotta love tools with a rest api

hacked up a quick home assistant module for py3status, and now my PC will yell at me when my brain is being degraded

I had to explain to a Mac user today that, for my Linux laptop to warn me about low battery, instead of just shutting down, I had to download a script from GitHub and set it up in my #i3wm window manager. But that's a small price to pay for the freedom to customise my system exactly how I want - without deferring to some Apple engineers to decide "what's good for me."

I moved back to #i3wm in @fedora for a while and had a difficult time isolating my Xorg logs to hunt down a problem. Here's a post to help you find your Xorg logs and the metadata behind each log line in journald:

https://major.io/p/xorg-logs-fedora-journalctl/