Wait. I did a release of my video player the other day, I forgot to say it publicly! (This world is slowly turning upside down.)

I wrote that thing because neither #vlc nor #ffplay work properly on my #debian setup (there is jitter in the video).

For this new release I implemented screensaver skipping (before that I had to press a key every 10 min or the screen gets dark). Not sure it works for every setup though, it's ok on my #fvwm environment.

I had fun doing this!

http://sedcore.eu.org/vlb/

@osnews Still running #FVWM here after all those years. I used to use #KDE a lot (still use the applications), have tried #Gnome several times. Used #Awesome for a bit… #WindowMaker, #AfterStep… #FVWM I keep coming back to.

I basically have it mostly configured as a manual tiling window manager through a couple of keyboard shortcuts that allow me to open windows full-screen, ½-screen or ¼-screen.

This has worked well for over 10 years now.

It was born out of a love/frustration-relationship with #Fvwm. Love the customization and looks, but there are also some annoying bugs. Looking around for other WM's I couldn't found one with the same feature-parity.

So here we are, the fruit of a manic period of researching a dying window system (X11) to build something that's already built into the WM I'm currently using, but "it could be nice to have just in case". :blobcatdunno:

Dispatches from the twilight of #X11: Debian has patched #FVWM 2 (following upstream, backported from FVWM 3) to deal with the reentrancy wackiness around how it handles expose events (https://github.com/somiaj/fvwm2-debian/commit/d4d1a7d8f66eddb09080c5f6a5b15f21b343b92a). Which has also backported the bug where icons don't repaint if they're exposed as part of a compound command or something like that.

Which happens to be something I do frequently as I navigate my chaotic pile of windows to get stuff done, so it's kind of annoying.

But! If I run `xcompmgr -a`, then repainting isn't a problem anymore, because ✨compositing✨ takes care of it I guess? (Other operating modes of `xcompmgr` spew BadPicture errors and fill windows with static.) So uh. I guess things work now.

Random question on the subject of #Linux window managers.

Is anyone out there still using #FVWM? And if so, how are you integrating "modern" needs (e.g. network config, battery monitoring)?

I have really fond memories of using #FVWM2 back in the day, before moving on to #Openbox.

Here's another nostalgia / #retrocomputing screenshot from 25 years of me running #Linux. This is from 2011, I did some years as a KDE exile, but here's back to #fvwm. A bit of a flat look, but more Win95 than Win10, last the last screenshot.

My notes says the panel is xfpanel, probably part of Xfce(?) I have tried *many* panels over the time, my computing environment is mostly scavenged from projects all over the place.

Wallpaper is a photo taken by me.

I’ve recently discovered that I’m sadly out of date regarding modern Unix windowing systems. So I figured I’d get a workstation set up to see what #Linux, #FreeBSD & #Illumos have been up to. But of course, I set up this #freebsd on #aarch64 system like a server first, so now I can’t seem to get #GNOME or even #fvwm running.

So yes, just like in 1999 I’m running #blackbox because it’s the only #X11 window manager as stupid as I am.

Debian's packaging for 1.8.4 removed a bunch of patches reverting upstream commits, opining that they shouldn't be needed anymore.

Some of the patch names mention reentrancy in `X*IfEvent` which is making me uneasy, because IIRC #fvwm does some “fun” things with that (i.e., the predicate callback ends up being hugely side-effecting and calls back into Xlib, for reasons beyond my ken). But I don't get what that would have to do with the crash I'm seeing.

(Also: lol, one of the libx11 commits specifically calls out fvwm2 for nesting XCheckIfEvent inside itself and making them need a counter for the nesting level insrtead of a flag.)

Continuing the 25-year journey through my #Linux screenshots.

Here's one from 2000 where I connect to my #Amiga 4000 via vnc, ironically watching Microsoft's website in the Voyager web-browser.

#gkrellm on the right, a faithful companion even now. And as always #fvwm as window manager (almost always, I cheated with KDE for a while).

Here's an old screenshot. The wm is #fvwm and it uses my custom fvwm-configuration, somewhat inspired by the #Amiga workbench both in looks and functionality. My current config still has that philosophy, although it's constantly evolving.

GifComposer is an old application I made for the Amiga BTW, and I guess that's supposed to be a logo I'm designing in Gimp.

Nostalgia-warning :linux:

It seems I celebrate 25 years as a #Linux -user this year. Found some old mail-conversations from that time with a friend where I instructed him how to configure #FVWM in #Redhat (must have been RH 5) with the so called NextLevel-configuration. Which basically was a bunch of m4-scripts for (imo) complicating the FVWM-setup :blobcatdunno: . I instructed him how to disable this NextLevel-stuff so he can edit the fvwmrc normally :blobcatgrimacing:

@jhx Floating, specifically #fvwm. Tried a tiling wm once but couldnt get into it. I guess I'm pretty stuck in my ways; for example I still use some #Amiga-like window management :blobcatgooglyshrug:

Hey hey hey, now we can start theming it...
#fvwm #fvwm3 #trisquel #emacs #eshell

Built from source, that's why I'm so happy about it.

My desktop environment 20 years ago. Sitting in front of a B&W (not gray!) NCD X Terminal. Hacking #postscript for my zine. Sidebar was a few vmstat displays of various machines, FvwmIconMan, virtual desktops, clock, and X cut buffers.

(My current desktop has actually changed very little since then.)

#ThrowBackThursday #retrocomputing #fvwm

@prahou default install, check
cd /usr/X22R6/lib/X22/fvwm
grep -r CursorMove
#fvwm #openbsd

I have to admit something. And I hope you all don't think less of me. I actually like fvwm. #openbsd #fvwm

TIL that updating #FVWM 2.x to FVWM 3 and adding `EdgeThickness 1` to my configuration file was enough to say goodbye to the annoyance of moving the cursor to the screen with higher vertical resolution to scroll up/down on the edge of the screen.

This make EdgeScrolling way more convenient when using monitors of different resolutions of orientations.

Running the default window manager #fvwm in #openbsd is really a throwback to the 1990s when I started using Unix/Linux-based systems.However, #openbsd "just works" ! Still need to figure out why my #ncurses color palette doesn't work identically there compared to #freebsd, #linux, and even #osx.

@james #fvwm crystal in #win95 mode. If anything it's better than the original Windows 95.

@snowdusk Nice desktop! I'm glad you seem to like #FVWM. (You misspelled that hashtag)