#fvwm3 #fvwm #wm #archaicsoftware

Hey everyone.

I've just released fvwm3-1.1.3, the details of which you can find here:

https://github.com/fvwmorg/fvwm3/releases/tag/1.1.3

Not many features or changes in this release other than the usual bout of bug-fixes.

However, as I've bleated on about before, this release is significant in that autotools has been removed, and meson has replaced it.

This means you have to use meson or muon to build fvwm3.

The release notes mention this, but I know some will miss it. Again though, more information here:

https://github.com/fvwmorg/fvwm3/discussions/1068

Let me know if you run into any issues.

Charming story of struggle and finding peace in #FVWM If you like those old Linux vibes.
I myself once spent a week struggling with FVWM on #OpenBSD . But OpenBSD, alas, has very old version in base, circa 2002 due to licensing reasons. So I couldn't do many things I wanted to do.
FVWM feels extremely strange and simply crazy when you delve into config files. But then configuration syntax starts to make sense and you feel you can do just about anything with it. I couldn't, though. =(
https://homeforaday.org/fvwm/

Interessant, wo überall bei #Linux festgelegt wird, welches Programm wofür zuständig ist. Wir haben Debians update-alternatives, ~/.config/mimeaps.list (die lauter Zombie-Einträge enthält, wenn es im Laufe der Zeit schon einige Deinstallationen gab), die KDE-Einstellung für Standardprogramme, die Firefox- und Thunderbird-internen Einstellungen dafür, ~/.mailcap (okay, die nutze ich nur für Mutt)...

Und bei #Fvwm blicke ich noch gar nicht durch, da ist es von Programm zu Programm unterschiedlich. Manche respektieren nicht einmal die Mimeapps-Liste oder update-alternatives, sondern bieten mir eine Auswahl von Programmen zum Öffnen an, die exakt 0 Einträge enthält (und Einträge, die ich optimistisch neu hinzufüge, im Nirvana ablegt).

Da ist bei meinem Fvwm noch Baustelle... Aber wir wollen ja lernen, wie das funktioniert. Also ich will.

#fvwm #fvwm3

fvwm3-1.1.1 has been released!

See: https://github.com/fvwmorg/fvwm3/releases/tag/1.1.1

Note that this release represents a good nine months worth of work. In that time, there's been five new contributors (thanks to you!).

This release is notable for a few things:

1. There is a new buildsystem -- meson is replacing autotools. As from this date (2024-NOV-30), there is now a six-month timer on autools support in fvwm3. On Friday 30th May 2025, I will be removing autotools from the fvwm3 repository. meson will be the default at that point.

See: https://github.com/fvwmorg/fvwm3/discussions/1068

2. FvwmRearrange has been completely overhauled, and has a number of nifty options to control placement. Do please take a look at some of the options and examples in `man FvwmRearrange`.

3. FvwmPager has received some further updates for `is_shared` mode.

4. Moving windows and maximizing them has now gained some further options:

Moving windows can now honour window boundaries (see the `all_windows` and `both_sides` options to the `Move` command).

You can now maximize a window to honour the window below to make another window the same size: `Maximize both_sides True grow grow`.

There's also been a bunch of other changes too numerous to list here. See the release notes for more information.

Special thanks for this release has to go to Matt Jolly for all his hard work on getting meson working with fvwm.

Also, to Jaimos Skriletz for his hard work on FvwmPager, FvwmRearrange, and other areas/bug-fixes.

Let the numerous other bugs introduced with this release haunt us all!

Enjoy!

With #xterm hiding all of its usability and #fvwm being not as popular as it should be: I’m starting to think that Wayland was a huge mistake. It may remove the screen tearing and be more secure, but it ensures that people coming into *nix won’t see how great it used to be.

Ot may not be systemd level of apocalypse. But it’s also in line with its love for modern apple - screw history. Fire the wrecking ball, we’ve got new stuff to build.

year of the desktop pajamas

Ok, I have a #portability issue to fix in #Xmoji. As reported by @0x1eef, it does not build on #OpenBSD. Seems OpenBSD doesn't provide the "#POSIX interval timers":

https://github.com/Zirias/xmoji/issues/4

I guess that's possible to fix by writing code to multiplex the single timer offered by setitimer(). Of course, that's exactly what I wanted to avoid by using the POSIX interval timers.

Is there any good alternative for OpenBSD? What are other projects doing? @thomasadam, does #fvwm need timers and, if so, how is it solved there?

Since desktop environments can always change and many new releases came out since last year, I would like to know which desktop environment you currently use?

#gnome #kdeplasma #xfce4 #cinnamondesktop #matedesktop #budgiedesktop #lxqt #linuxdesktop #linux #freebsd #openbsd #netbsd #i3wm #bspwm #xmonad #dwm #fvwm #qtile #wayland #xorg

* Multiple choices possible

I know I sound like an old man, but...come ON. There's no way to make a #gnome launcher without *editing an arcane text file*?

If it's going to work like the early 90s, can we just go back to #fvwm ?

"about the impertinence of good software"

#fvwm #fvwm3

Hi all,

#fvwm3 version 1.1.0 has been released.

This release does contain fixes to bugs, as well as several different improvements to FvwmPager.

For the general release notes, please see: https://github.com/fvwmorg/fvwm3/releases/tag/1.1.0

For specific details on some of the bigger changes (especially breaking changes), see: https://github.com/fvwmorg/fvwm3/discussions/983

One thing to note for anyone who packages fvwm3 for their Linux distribution, or maintains a port of it in BSD, libXFT has now been made a core dependency, and is no longer optional. AFAICT, this seems to have been the case for most packagers, but I thought I'd mention it here.

Enjoy!