#fvwm3 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #fvwm3, aggregated by home.social.
-
CoW has now gained a new "module" -- cowident.
The image below shows what it does. When you run it, it will force you to select a window to then report properties on.
It's analogous to FvwmIdent from #fvwm3
Not the sexiest thing in the world, I know, but maybe useful both for those tweaking their config, and for diagnostic purposes.
That's why #FvwmIdent was created -- to allow for diagnostics.
-
CoW has now gained a new "module" -- cowident.
The image below shows what it does. When you run it, it will force you to select a window to then report properties on.
It's analogous to FvwmIdent from #fvwm3
Not the sexiest thing in the world, I know, but maybe useful both for those tweaking their config, and for diagnostic purposes.
That's why #FvwmIdent was created -- to allow for diagnostics.
-
CoW has now gained a new "module" -- cowident.
The image below shows what it does. When you run it, it will force you to select a window to then report properties on.
It's analogous to FvwmIdent from #fvwm3
Not the sexiest thing in the world, I know, but maybe useful both for those tweaking their config, and for diagnostic purposes.
That's why #FvwmIdent was created -- to allow for diagnostics.
-
CoW has now gained a new "module" -- cowident.
The image below shows what it does. When you run it, it will force you to select a window to then report properties on.
It's analogous to FvwmIdent from #fvwm3
Not the sexiest thing in the world, I know, but maybe useful both for those tweaking their config, and for diagnostic purposes.
That's why #FvwmIdent was created -- to allow for diagnostics.
-
CoW has now gained a new "module" -- cowident.
The image below shows what it does. When you run it, it will force you to select a window to then report properties on.
It's analogous to FvwmIdent from #fvwm3
Not the sexiest thing in the world, I know, but maybe useful both for those tweaking their config, and for diagnostic purposes.
That's why #FvwmIdent was created -- to allow for diagnostics.
-
Let's play spot the difference!
One, both, or none of two screenshots are from fvwm3.
Can you guess which?
If not, could you maybe guess is one of the screenshots is based on wayland? ;)
In all seriousness, I'm trying to emulate the fvwm/mwm look in #hikari -- and I think the results are impressive, especially if you can't tell which image is from which #wm.
-
Let's play spot the difference!
One, both, or none of two screenshots are from fvwm3.
Can you guess which?
If not, could you maybe guess is one of the screenshots is based on wayland? ;)
In all seriousness, I'm trying to emulate the fvwm/mwm look in #hikari -- and I think the results are impressive, especially if you can't tell which image is from which #wm.
-
Let's play spot the difference!
One, both, or none of two screenshots are from fvwm3.
Can you guess which?
If not, could you maybe guess is one of the screenshots is based on wayland? ;)
In all seriousness, I'm trying to emulate the fvwm/mwm look in #hikari -- and I think the results are impressive, especially if you can't tell which image is from which #wm.
-
Let's play spot the difference!
One, both, or none of two screenshots are from fvwm3.
Can you guess which?
If not, could you maybe guess is one of the screenshots is based on wayland? ;)
In all seriousness, I'm trying to emulate the fvwm/mwm look in #hikari -- and I think the results are impressive, especially if you can't tell which image is from which #wm.
-
Let's play spot the difference!
One, both, or none of two screenshots are from fvwm3.
Can you guess which?
If not, could you maybe guess is one of the screenshots is based on wayland? ;)
In all seriousness, I'm trying to emulate the fvwm/mwm look in #hikari -- and I think the results are impressive, especially if you can't tell which image is from which #wm.
-
Throwing this out there, I guess: anyone have a suggestion for a Fvwm3 replacement in Wayland? I’m having trouble finding a comparatively minimal Wayland compositor with the same kind of low-level flexibility—and, as stupid as it is, the capability to look like a hybrid between CDE and Window Maker. #fvwm #fvwm3 #wayland #linux
-
I've released fvwm3 version 1.1.4
Changelog/release is here:
https://github.com/fvwmorg/fvwm3/releases/tag/1.1.4
Not too much to write home about, other than a few improvements to RandR, as well as a change to make FvwmForm more UTF8-aware.
Thanks to everyone who helped contribute to this release, it's appreciated!
Enjoy!
-
#fvwm3 #autotools #meson #buildsystems
A little over six months ago, I said the following:
https://bsd.network/web/@thomasadam/113340194570527011
Since six months has passed, I've now pushed to `main` a PR which does just that -- removes autotools from #fvwm3 and replaces it with meson:
https://github.com/fvwmorg/fvwm3/pull/1191
So this has been your warning.
When I release fvwm3-1.1.3, it will be using meson only.
Any questions, please do let me know. I hope downstream packagers have made the transition. :)
-
What's that? You want to wait for the OOM-killer to come along, and you're using #fvwm?
Sure, no problem:
```
Style * PositionPlacement UnderMouse, InitialMapCommand ForkBombDestroyFunc ForkBomb
AddToFunc ForkBomb
+ I Exec exec xtermDestroyModuleConfig FEF: *
*FEF: focus_change ForkBombModule FvwmEvent FEF
```:)
-
#fvwm3 #autotools #meson #muon #buildsystem
Hey all! Please note that although fvwm3-1.1.1 is close to being relesaed, there's still a few more things left to do.
Before that point, I'd like to take the opportunity to mention that as of fvwm3-1.1.1 fvwm3 is officially using meson/muon as the buildsystem of choice.
Autotools has been a tremendous help over the years. Heck, fvwm as a project started long before autotools existed.
But as technology changes, newer buildsystem alternatives have come along making better use of hardware, compilation speeds, etc.
Indeed, because of fvwm's age -- there's a tonne of custom m4 macros -- some of which are to work around issues long since gone. With autotools recently deprecating many of these, maintaining this was becoming difficult. Hence the change.
A six-month window exists once fvwm3-1.1.1 is released for downstream packagers to make the move from autotools to meson.
The `main` branch in the fvwm3 repository contains both buildsystems. Please give meson some testing!
A huge thanks goes to Kanjie (Matt Jolly) -- without whom none of this work would have been possible. Thanks, Matt!
For more specific details. please see: https://github.com/fvwmorg/fvwm3/discussions/1068
Questions? I'm here...
-
@dani Haha 😎
I'm running a (heavily configured) #fvwm3 here. This screenshot was just for demonstration that #dos2ansi and #showansi don't depend on any configuration, so this was a completely unconfigured X session in #Xephyr, which by default runs #twm.
You can even see the test mode in #xterm can only use 8 colors (because this is what the default xterm #terminfo entry announces), still the #xterm windows launched by #showansi have full color support, they explicitly set the terminal name to "xterm-256colors".
-
#fvwm3 actually merged my "pull request" to add some .desktop file for the #XSession upstream, a topic that came up in a #FreeBSD #ports PR.
It was very quick, and during review conversations, I even learned that KDE delivers a "broken" .desktop file (by FDO standards) which somehow still works 🙈
Anyways, kudos for handling it that quickly. Any porter/packager is thankful for upstreams *that* responsive! 👍
https://github.com/fvwmorg/fvwm3/commit/b3bd394a87d4caab846e1e36be560330901bef27 -
For #fvwm1 (and for a time, #fvwm2), the man page used to have a BUGS section which listed the following:
As of fvwm 0.99 there were exactly 39.342 unidentified bugs. Identified bugs have mostly been fixed, though. Since then 9.34 bugs have been fixed.
Assuming that there are at least 10 unidentified bugs for every identified one, that leaves us with 39.342 - 9.32 + 10 * 9.34 = 123.402 unidentified bugs. If we follow this to its logical conclusion we will have an infinite number of unidentified bugs before the number of bugs can start to diminish, at which point the program will be bug-free.
Since this is a computer program infinity = 3.4028e+38 if you don't insist on double-precision. At the current rate of bug discovery we should expect to achieve this point in 3.37e+27 years
I guess I better plan on passing this thing on to my children....
The "I" here refers to Robert Nation, the original creator of #fvwm and #rxvt.
As it happens, I've not been able to reduce the number of bugs in #fvwm3 either, and I've no grandchildren...