#fvwm3 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #fvwm3, aggregated by home.social.
-
@mxchara #FVWM3 here, watching it's river-based #CompositorOnWayland successor closely though.
-
@mxchara #FVWM3 here, watching it's river-based #CompositorOnWayland successor closely though.
-
@mxchara #FVWM3 here, watching it's river-based #CompositorOnWayland successor closely though.
-
@mxchara #FVWM3 here, watching it's river-based #CompositorOnWayland successor closely though.
-
More from me!
This time, icons...
With this change, icons are now more of a first-class citizen in CoW.
It's possible to assign icons (either SVG or PNG) to windows, via the `decor` command.
The cow(!) man page has a dedicated icon section so you can see how to do that.
By default, cow ships with an icon which mimics what MWM has.
Icons can now be moved around the desktop, and windows remember their icon position.
The new icon-reset command will put icons back to their default position, which is managed by cow. This is similar to the `PlaceAgain icon` command from #fvwm and #fvwm3
Enjoy!
-
More from me!
This time, icons...
With this change, icons are now more of a first-class citizen in CoW.
It's possible to assign icons (either SVG or PNG) to windows, via the `decor` command.
The cow(!) man page has a dedicated icon section so you can see how to do that.
By default, cow ships with an icon which mimics what MWM has.
Icons can now be moved around the desktop, and windows remember their icon position.
The new icon-reset command will put icons back to their default position, which is managed by cow. This is similar to the `PlaceAgain icon` command from #fvwm and #fvwm3
Enjoy!
-
More from me!
This time, icons...
With this change, icons are now more of a first-class citizen in CoW.
It's possible to assign icons (either SVG or PNG) to windows, via the `decor` command.
The cow(!) man page has a dedicated icon section so you can see how to do that.
By default, cow ships with an icon which mimics what MWM has.
Icons can now be moved around the desktop, and windows remember their icon position.
The new icon-reset command will put icons back to their default position, which is managed by cow. This is similar to the `PlaceAgain icon` command from #fvwm and #fvwm3
Enjoy!
-
More from me!
This time, icons...
With this change, icons are now more of a first-class citizen in CoW.
It's possible to assign icons (either SVG or PNG) to windows, via the `decor` command.
The cow(!) man page has a dedicated icon section so you can see how to do that.
By default, cow ships with an icon which mimics what MWM has.
Icons can now be moved around the desktop, and windows remember their icon position.
The new icon-reset command will put icons back to their default position, which is managed by cow. This is similar to the `PlaceAgain icon` command from #fvwm and #fvwm3
Enjoy!
-
Hello all,
fvwm3-1.1.5 has been released.
See:
https://github.com/fvwmorg/fvwm3/releases/tag/1.1.5
This is mostly a bug-fix release. FvwmPrompt has been simplified which I hope eases issues with downstream maintainers.
FvwmConsole has now gone -- use FvwmCommand or FvwmPrompt.
Enjoy!
-
Hello all,
fvwm3-1.1.5 has been released.
See:
https://github.com/fvwmorg/fvwm3/releases/tag/1.1.5
This is mostly a bug-fix release. FvwmPrompt has been simplified which I hope eases issues with downstream maintainers.
FvwmConsole has now gone -- use FvwmCommand or FvwmPrompt.
Enjoy!
-
Hello all,
fvwm3-1.1.5 has been released.
See:
https://github.com/fvwmorg/fvwm3/releases/tag/1.1.5
This is mostly a bug-fix release. FvwmPrompt has been simplified which I hope eases issues with downstream maintainers.
FvwmConsole has now gone -- use FvwmCommand or FvwmPrompt.
Enjoy!
-
Hello all,
fvwm3-1.1.5 has been released.
See:
https://github.com/fvwmorg/fvwm3/releases/tag/1.1.5
This is mostly a bug-fix release. FvwmPrompt has been simplified which I hope eases issues with downstream maintainers.
FvwmConsole has now gone -- use FvwmCommand or FvwmPrompt.
Enjoy!
-
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.
-
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
-
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
-
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
-
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
-
@trashheap For reasons I have long forgotten, #FVWM3. It floats my boat and drowns the bloat.
-
@trashheap For reasons I have long forgotten, #FVWM3. It floats my boat and drowns the bloat.
-
@trashheap For reasons I have long forgotten, #FVWM3. It floats my boat and drowns the bloat.
-
@trashheap For reasons I have long forgotten, #FVWM3. It floats my boat and drowns the bloat.
-
@kerravonsen @LovesTha Yes, fvwm isn't a tiling window manager, but in #fvwm3, we've put some interesting changes into FvwmRearrange which you might find interesting.
Furthermore, there's always been this:
Maximize grow grow
Which you bound to a key, for instance, would maximise the given window to fill the available space. In this way you can quickly "tile" windows.
-
@kerravonsen @LovesTha Yes, fvwm isn't a tiling window manager, but in #fvwm3, we've put some interesting changes into FvwmRearrange which you might find interesting.
Furthermore, there's always been this:
Maximize grow grow
Which you bound to a key, for instance, would maximise the given window to fill the available space. In this way you can quickly "tile" windows.
-
@kerravonsen @LovesTha Yes, fvwm isn't a tiling window manager, but in #fvwm3, we've put some interesting changes into FvwmRearrange which you might find interesting.
Furthermore, there's always been this:
Maximize grow grow
Which you bound to a key, for instance, would maximise the given window to fill the available space. In this way you can quickly "tile" windows.
-
@kerravonsen @LovesTha Yes, fvwm isn't a tiling window manager, but in #fvwm3, we've put some interesting changes into FvwmRearrange which you might find interesting.
Furthermore, there's always been this:
Maximize grow grow
Which you bound to a key, for instance, would maximise the given window to fill the available space. In this way you can quickly "tile" windows.
-
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!
-
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!
-
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!
-
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!
-
I’m sick of fighting just to get even simple automated window geometries to work consistently and sanely with #Wayland.
So I went back to the roots and discovered there is actually an #FVWM3 now!
Perfect geometries. Everything under control. Lightning fast and light. And even sound is way better directly through ALSA.
Funny how it feels amazing for my computer to work for me again, instead of me trying in vain to work with it.
-
I’m sick of fighting just to get even simple automated window geometries to work consistently and sanely with #Wayland.
So I went back to the roots and discovered there is actually an #FVWM3 now!
Perfect geometries. Everything under control. Lightning fast and light. And even sound is way better directly through ALSA.
Funny how it feels amazing for my computer to work for me again, instead of me trying in vain to work with it.
-
I’m sick of fighting just to get even simple automated window geometries to work consistently and sanely with #Wayland.
So I went back to the roots and discovered there is actually an #FVWM3 now!
Perfect geometries. Everything under control. Lightning fast and light. And even sound is way better directly through ALSA.
Funny how it feels amazing for my computer to work for me again, instead of me trying in vain to work with it.
-
I’m sick of fighting just to get even simple automated window geometries to work consistently and sanely with #Wayland.
So I went back to the roots and discovered there is actually an #FVWM3 now!
Perfect geometries. Everything under control. Lightning fast and light. And even sound is way better directly through ALSA.
Funny how it feels amazing for my computer to work for me again, instead of me trying in vain to work with it.
-
#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.
-
#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.
-
#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.
-
#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.
-
I had the fun of #fvwm3 segfaulting on my config… not quite sure what it was barfing on because even `fvwm3 -v` just segfaulted without any meaningful logs given… but I think it was related to a `PipeRead` judging from the `gdb` backtrace of the `core` file.
The config I have is based on what was an example config from FVWM2 circa 2009 when I was tuning it on an old Pentium II 300MHz laptop (which I now have #NetBSD on)
So I started afresh, and brought over the settings I specifically cared about, my key bindings. I managed to bring the window decorations across too.
Not hugely big on the permanent side-bar… I had a Logo,Z key sequence to hide/show it on the old config so I could use a near full screen… but we'll see how it goes.
-
I had the fun of #fvwm3 segfaulting on my config… not quite sure what it was barfing on because even `fvwm3 -v` just segfaulted without any meaningful logs given… but I think it was related to a `PipeRead` judging from the `gdb` backtrace of the `core` file.
The config I have is based on what was an example config from FVWM2 circa 2009 when I was tuning it on an old Pentium II 300MHz laptop (which I now have #NetBSD on)
So I started afresh, and brought over the settings I specifically cared about, my key bindings. I managed to bring the window decorations across too.
Not hugely big on the permanent side-bar… I had a Logo,Z key sequence to hide/show it on the old config so I could use a near full screen… but we'll see how it goes.
-
I had the fun of #fvwm3 segfaulting on my config… not quite sure what it was barfing on because even `fvwm3 -v` just segfaulted without any meaningful logs given… but I think it was related to a `PipeRead` judging from the `gdb` backtrace of the `core` file.
The config I have is based on what was an example config from FVWM2 circa 2009 when I was tuning it on an old Pentium II 300MHz laptop (which I now have #NetBSD on)
So I started afresh, and brought over the settings I specifically cared about, my key bindings. I managed to bring the window decorations across too.
Not hugely big on the permanent side-bar… I had a Logo,Z key sequence to hide/show it on the old config so I could use a near full screen… but we'll see how it goes.
-
I had the fun of #fvwm3 segfaulting on my config… not quite sure what it was barfing on because even `fvwm3 -v` just segfaulted without any meaningful logs given… but I think it was related to a `PipeRead` judging from the `gdb` backtrace of the `core` file.
The config I have is based on what was an example config from FVWM2 circa 2009 when I was tuning it on an old Pentium II 300MHz laptop (which I now have #NetBSD on)
So I started afresh, and brought over the settings I specifically cared about, my key bindings. I managed to bring the window decorations across too.
Not hugely big on the permanent side-bar… I had a Logo,Z key sequence to hide/show it on the old config so I could use a near full screen… but we'll see how it goes.
-
#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. :)
-
#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. :)
-
#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. :)
-
#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. :)