#fvwm — Public Fediverse posts

@gumnos

Oh man, yeah. I never put anything in {,/usr}/{,s}bin except the occasional symlink.

I want to try a pure "just use base" install of #OpenBSD sometime. ;)

cwm is kinda neat, a wee bit reminiscent of #dwm or #rio, but definitely on the mousey side.

The default theme of the version of #fvwm they ship is kinda too colorful, but I'm sure it's extremely configurable... if I can only learn the rather elaborate config setup for it.

#cow #fvwm #wayland

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 #fvwm #wayland

Currently working on squeeze titlebars.

This is something which some people wanted in fvwm, and it actually comes from #ctwm, whereby the titlebar was squeezed to its length so it didn't take up the whole width of the window.

Wayland doesn't have any shape support (a la XShape extension) so doing this manually is tricky.

Anyway, screenshot attached of what squeezed titlebars will look like in CoW. Options for left, centre, or right aligned.

#cow #fvwm #wayland

Currently working on squeeze titlebars.

This is something which some people wanted in fvwm, and it actually comes from #ctwm, whereby the titlebar was squeezed to its length so it didn't take up the whole width of the window.

Wayland doesn't have any shape support (a la XShape extension) so doing this manually is tricky.

Anyway, screenshot attached of what squeezed titlebars will look like in CoW. Options for left, centre, or right aligned.

#cow #fvwm #wayland

Currently working on squeeze titlebars.

This is something which some people wanted in fvwm, and it actually comes from #ctwm, whereby the titlebar was squeezed to its length so it didn't take up the whole width of the window.

Wayland doesn't have any shape support (a la XShape extension) so doing this manually is tricky.

Anyway, screenshot attached of what squeezed titlebars will look like in CoW. Options for left, centre, or right aligned.

#cow #fvwm #wayland

Currently working on squeeze titlebars.

This is something which some people wanted in fvwm, and it actually comes from #ctwm, whereby the titlebar was squeezed to its length so it didn't take up the whole width of the window.

Wayland doesn't have any shape support (a la XShape extension) so doing this manually is tricky.

Anyway, screenshot attached of what squeezed titlebars will look like in CoW. Options for left, centre, or right aligned.

#cow #fvwm #wayland

Currently working on squeeze titlebars.

This is something which some people wanted in fvwm, and it actually comes from #ctwm, whereby the titlebar was squeezed to its length so it didn't take up the whole width of the window.

Wayland doesn't have any shape support (a la XShape extension) so doing this manually is tricky.

Anyway, screenshot attached of what squeezed titlebars will look like in CoW. Options for left, centre, or right aligned.

@thomasadam I would love to try it out as I'm a big fan of #fvwm as well. Unfortunately I'm on Debian stable so it would be a lot of effort to compile everything...

#fvwm

In 2003, fvwm launched a logo competition:

http://www.fvwm.org/fvwm-ml/10502.html

This was to coincide with fvwm's tenth birthday.

Several suggestions were put forward, as is archived here:

https://www.fvwm.org/Archive/Logos/

This was the winning entry -- there's links from the top of that page to past entries.

I just think it's a lovely piece of window manager history -- and shows the number of users who cared about this.

That was #fvwm in its prime -- alas, not any longer. :)

#cow #fvwm #wayland

Hey all. For anyone who's following along. I've just merged support for pages in #cow.

This is also accompanied with a pager.

From what testing I've done, this seems to work for me -- no doubt there's bugs.

The example config in the repo shows what you which settings to enable to make pages work.

If you're interested in giving it a go, please do!

#fvwm #x11 #wm

In case anyone's wondering, even though I'm working on #cow-wayland, I'm still working on, and fixing, #fvwm3 -- I don't see this changing anytime soon.

#fvwm #mwm #wm #wayland

Hello everyone, and Happy Easter!

I've been busy trying to get to this point, and I'm finding it useable enough that I wanted to mention it here.

I'm releasing some code!

cow, is a "Compositor on Wayland", which aims to look-and-feel like mwm and fvwm from X11, but instead, running on wayland.

https://codeberg.org/thomasadam/cow

The README.md (screenshot), and associated config file example should be enough to get you started for now, if you're interested.

There's still a tonne of things to do before I even consider a release -- and no doubt there's a shed load of bugs, etc.

So if you're interested in using a wayland window manager that looks like it's stuck in the early 90s, give this thing a go.

An IRC channel exists on libera.chat -- #cow-wayland if you want to come and say "hello".

Any issues... err, chuck an issue on Codeberg, please. Note that I won't be providing any mirrors of this on GH. Codeberg is where this project is officially hosted.

lovely minimalist black-white-gray window arrangement with almost no style of prompts or vim (easily build with #fvwm)

https://cdn.deskto.ps/images/864406672789024770.png

another weekend of tweaking #fvwm to my liking (inspired by /r/unixporn which still has some good wm stuff)

found some interesting minimalist gray/black/white styles and an example reviving the whole "desktop bigger than screen" size I used 30 years ago (literally) a lot 😂 https://www.reddit.com/r/unixporn/comments/1rw4e1z/driftwm_infinite_canvas_wayland_compositor_no/

(still undecided in terms of userinterface how and what I want from my prompt, my window titles etc and where to display it all. e.g. starship's language icons are meaningless for me or git state)

#fvwm #fvwm3 #wayland

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.

SSD not CSD

The nice thing about that period, is that everything was keyboard driven and the mouse was only used when it was handy. The great thing about that period, is that you could do everything literally everything with your keyboard and the user interfaces were much more simple to design, modify and to expand, because it was much easier for the programmers to determine what you want based upon the fact that you are using the keyboard as input.

It started to go downhill when the scrollwheel was added.

Three buttons were enough.

Everything degenerated to CSD, while SSD is the proper way to go, and we now have hacks to force SSD in different Linux distributions. Hopefully the BSD flavours have such hacks too

If you still want SSD as much as possible, you need to use fluxbox as your DM / WM and use the considerable tweaks that @rl_dane has suggested to me in another toot in this thread, get firefox to behave normally again. You should also disable all the silly LLM stuff in ffox...
Im going to put the tweaks at work here on this SBC Pi5, I'm currently on

@tragivictoria  @Radio_Azureus @magitian

#GUI #TUI #design #40years #fvwm #twm #Xorg #programming #technology #DE #desktop #environment #WM #window #manager #FluxBox #XFCE #KDE #GNOME #design

# CSD
Reading up on CSD, client side decorations

Client side decorations give a lot of headaches when they're not properly implemented many of these mods should just stay with SSD, server side decorations

Quote
> GtkHeaderBar merges the title bar, menu bar and tool bar into one unified horizontal bar to give more space to the application content, potentially reducing the amount of wasted space by showing empty bars.

https://en.wikipedia.org/wiki/Client-side_decoration?wprov=sfla1

#GUI #TUI #CSD #design #40years #fvwm #twm #Xorg #programming #technology #DE #desktop #environment #WM #window #manager #FluxBox #XFCE #KDE #GNOME #design

You're absolutely right there are worse things occuring.

But the following is a bad CSD

CSD In Firefox mobile

• Something odd was changed in the user interface; the sidebar it's actually the menu that you get when you tap on the double point in the lower right corner, was transformed into this massive monstrosity which covers the whole Android display.
• It distracts
• All the extra information is useless
• it takes many more GPU Cycles to throw that big thing on the screen
• no one was consulted within the user base would tell them that it just makes everything worse, because you don't see anything underneath

CSD Enshittification Factor

Instead of going on I'll just stick with what that still works I may need to go all the way back to that MX Linux distro which at least feels familiar and use as many clients that don't abuse CSDs

One more question; what example do you have of something that's worse than client-side decorations

IMHO the one I just referred too, is a very bad one

Quote Wikipedia:

Limitations
If the application hangs, the user cannot close it by clicking the close button in the window frame.[12]

BTW to prove your point;

It took me 15 minutes to compose this lousy small message on the Android. It would have taken me 120 seconds on one of the desktops running here
All because of horrific user interfaces low free RAM and bad CSD choices on the Android

https://en.wikipedia.org/wiki/Client-side_decoration?wprov=sfla1

#GUI #TUI #CSD #design #40years #fvwm #twm #Xorg #programming #technology #user #environment #DE #desktop #environment #WM #window #manager #FluxBox #XFCE #KDE #GNOME #design

@rl_dane @dendrobatus_azureus @magitian

@elithebearded @nina_kali_nina : My guess is #Fvwm

GUI TUI

Your response sheds a clear light on what's wrong, deeply wrong in this matter.

I stick to DE and window managers which feel and look like they're from decades ago. In those I don't face the horrible points you stated. I glanced at the theme on it's own and did not take these points into account.

From the perspective of UI design, many GUI's have been deliberately broken with the thin and disappearing scroll bars which are a *PITA and the removal of the menu bar by default in this bloody browser I work in ATM within standardnotes. There is so much broken in those things I would need to type a whole book full, yet very few would read it.
I always find workarounds which is what I stated in the previous stansa.

You're right that 40 years of meticulous UI design, craft and tweaking should be cherished and expanded. I wonder why this trend started

I loved working in fvwm & twm and did it for years

Are there still Window and Desktop Managers left which are currently maintaned and follow the priciples as strickt as possible? What do you think of KDE in this light?

Note:
I use XFCE as my DE and love the other light one in the MX Linux distro FluxBox. The older it is the better I can fly thorugh it with my keyboard and windows behave in a standard way

@rl_dane @Radio_Azureus @magitian

#GUI #TUI #design #40years #fvwm #twm #Xorg #programming #technology #DE #desktop #environment #WM #window #manager #FluxBox #XFCE #KDE #GNOME #design

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

Installed Red Hat Linux 4.0 in a VM for testing purposes :p

#RetroComputing #Linux #RedHat #FVWM #OldSchoolLinux #VintageComputing

#fvwm #lwn

https://lwn.net/Articles/1053678/

This article was about x11 support, etc., and quickly devolved into something else entirely.

I shouldn't be surprised, but yet again, anyone who is anyone can/does have an opinion, which sucks.

Bei der Distro/Desktop-Entscheidung etwas anstrengend: es werden vor allem solche empfohlen, die möglichst windowsnah sind. Geht aber auch als Negativfilter. Daher jetzt der Download von T2-Mint mit Xfce und geplantem Upgrade zu fvm3 (ja, ich bin alt und habe eine Linux-Vergangenheit).
#fvwm #linuxmint

FVWM-95

https://fvwm95.sourceforge.net/

#HackerNews #FVWM95 #FVWM #WindowManager #OpenSource #DesktopEnvironment #RetroComputing

"#XLibre and #Nvidia…" Well, this one is dedicated to all the ABI breakage "experts":

Nvidia GeForce 210, Nvidia driver v340, XLibre with https://github.com/X11Libre/xserver/pull/658, #Slackware 15.0, #Linux 6.17.6, #Fvwm

More #liberatedscreens at https://github.com/orgs/X11Libre/discussions/211

I've taken the time to read this IT notes Story where we are reminded to use Open Source Code in the diverse way it's intended

I can give you an example regarding the _if tools_
**ifconfig** is in my _muscle memory_ the things that I need executed from this program just fly out of my fingers in reflex mode
I've been using the if tools ever since we needed to _compile everything_ ourselves, when we wanted to run an Open Source Environment, where the kernel was written and delivered in source code only.
If this is the first toot you read by me, I've been with the Open Source community on the Linux side since the alpha versions were coded and distributed through Usenet, in comp.os.unix.*

In that period you were grateful when a task set that you needed to execute, had a program, which would either make your task easier or better manageable, than doing everything by hand in a laborious manner

Ever since the beginning there are different GNU programs, written in the Richard Stallman period, that can do similar things. All you need to do is choose what you like and stick with it
If you do not like the way it works, you can fork it & change the code, if you don't know how to write a line of code, there are _manual pages_ available which you can use as teaching methods to learn how to code yourself
All you need to be for that is an _autodidact_
You have the power of the **Source Code** readily available right in front of you

At a certain point in time _Bram Molenaar_ did not like the way VI worked; he want it more than vi offered. At this point in time Bram Molenaar programmed vim on the _Amiga_ computer. Since the true Open Source form was followed vim was also distributed in Source form and was happily adopted by others who were thinking in a similar manner as Bram Molenaar and they started to contribute to that program.
vi is a vital program on UNIX systems. What Bram has made, is create a _choice_ for people who want it more than what vi offered.

# vim & vi happily coexist!

## This is the beauty of Open Source

At a later point in time this is also what happened with the programmer who wanted more than what the if-tool set offers. Thus the command set of _ip_ was programmed. Similar to vi and vim they happily coexist.

### However on the distribution level something changed.

After a couple of decades I noticed that traditional tools, that have been tried, tested, stable and have withstood the test of time, were dropped from the base installations. You have to go and fetch them yourself. It was even done with _critical tools_ like the if tool set. It's not just one distribution that's doing it but different distributions.
I was busy with an installation; at a certain point I needed **ifconfig** to work on my network interface devices; I needed to configure something on the fly. Imagine my facial expression when I detected that ifconfig wasn't in the base installation!
The machine was in a _chicken egg_ situation because I had &no access to the network_ I had to stop, go to another place fetch the if tools separately, find out that they were dropped for reasons which were totally irrelevant to my work, go back to the machine, install them separately and in the process waste many valuable minutes of time.

It was then that I started to notice the pattern a pattern of **polarization** removing tools which are critical to base installations without leaving a warning

I had to _change_ my setup routine which has been working for decades in a _flawless_ manner, because someone somewhere decided that a good tool set became obsolete.

This polarization is not only in the choice of what commands are chosen to be in the base installation of a distribution, it's in many different sections of the open source community which is what Stefano has shed some light upon.

Polarization because of diversity is totally unnecessary, happy and peaceful coexistance is key

* You can love vim yet cherish vi
* You can glorify emacs yet admire vim
* I can love XCFE cherish LXDE, admire KDE & like GNOME all simultaneously

Depending up on what I'm doing, what machine I am working on (SBC server embedded system), what is needed on the task at hand, I simply adapt and work with the diverse tools available for free.

There is absolutely now need for polarisation or Toxic behavior in the Open Source ENV:

Another example is the direction that Gnome went many years ago.

In that period I used Enlightenment, Gnome, KDE and FVWM simultaneously on different machines. All WM are working in a manner that I like. When however the Gnome programmers decided to strip configuration features of the Desktop Environment, I didn't go on a rant, I didn't bother to fork, because of the massive amount of work involved.

I just left in Peace

Diversity is Vital. GNOME is Vital! We need them all

🦋💙#Lobi 💙🦋

#Story #Stefano #Programming #FVWM #LXDE #OpenSource #BSD #freeBSD #Linux #POST #X86 #technology #SBC

https://my-notes.dragas.net/2025/11/14/this-isnt-a-battle/

The #FVWM developers have released version 1.1.4. of their FVWM3 #X11 window manager containing minor enhancements and bug fixes. Please see the announcement at https://github.com/fvwmorg/fvwm3/releases/tag/1.1.4 . #XLibre #Xingsday

#fvwm3 #fvwm

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!

rio-like configuration for base openbsd fvwm2

https://nein.triapul.cz/fvwm

#rio #fvwm #plan9 #openbsd #fishlinux #serpico

What are people's thoughts on the future of #X11 ?

The #Linux world is turning it's back on X in order to adopt #wayland

I suspect that similar things are getting to critical mass in the #BSD world.

Is X going to disappear entirely? Become super niche? Become abandoned? Remember xfree86?

I look to old window managers like #Openbox, #fvwm, #afterstep, and others and get all "misty eyed" about what will be lost.

#freebsd #runbsd #retrocomputing

#fvwm #smol #terminal #unix

I wonder whether I should do a write-up on how I use #linux/#unix the way I do?

I have spent all of my life living out of the terminal as much as possible, which has meant using certain programs to establish some kind of "workflow". I equally dislike how much I might have to use the browser. Although I use #telescope-browser with #gemini as much as I can!

I used to use #elinks (https://xteddy.org/elinks/) -- I believe this has been resurrected (https://github.com/rkd77/elinks). I'm also aware #dillo has also been revived.

There's so many of these types of articles though, and it can come across as a cliche -- which I would not want. But equally, I think there's merit in appreciating how other people use their computer to do $STUFF.

So... I'm not sure. If you think this might be interesting, let me know. I'll do it. Possibly, #gemini first, to prove a point? ;) ;)

#fvwm3 #fvwm #forkbomb

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 ForkBomb

DestroyFunc ForkBomb
AddToFunc ForkBomb
+ I Exec exec xterm

DestroyModuleConfig FEF: *
*FEF: focus_change ForkBomb

Module FvwmEvent FEF
```

:)

A pauta sobre easter eggs da #SegundaFicha cobre apenas jogos? Como um usuário #Linux da velha guarda, gostaria de resgatar o easter egg das antigas versões do Red Hat (incluindo o #Conectiva Red Hat Linux), que exibiam um chapéu giratório se uma determinada região do `timetool` (aplicativo para ajuste de data e hora) era clicada. Não achei captura de tela, então, precisei eu mesmo fazer uma (emulador PCem, distribuição Conectiva Red Hat Linux Marumbi).

🏷️ Etiquetas adicionais: #retrocomputing #redhat #fvwm #fvwm2 #anotherlevel #tcltk #emulacao #emulation

Episódio 156 – NeXT e NeXTSTEP – Parte B

https://retropolis.com.br/2024/09/11/episodio-156-parte-b/

#Podcast #AfterSTEP #AldusFreehand #AltsysVirtuoso #Apple #canon #CarnegieMellon #CERN #Cocoa #Copland #Darwin #Doom #DoomII #FVWM #GilAmelio #JohnCarmack #Linux #MacOSX #Mach #NeXT #NeXTSoftwareInc #NeXTCube #NeXTstation #NEXTSTEP #objectstation #ObjectiveC #OPENSTEP #PizzaBox #podcast #Postscript #Previous #Quake #Retrocomputao #Retrpolis #Rhapsody #SistemaOperacional #slab #SteveJobs #Tal

Episódio 156 – NeXT e NeXTSTEP – Parte B

https://retropolis.com.br/2024/09/11/episodio-156-parte-b/

#Podcast #AfterSTEP #AldusFreehand #AltsysVirtuoso #Apple #canon #CarnegieMellon #CERN #Cocoa #Copland #Darwin #Doom #DoomII #FVWM #GilAmelio #JohnCarmack #Linux #MacOSX #Mach #NeXT #NeXTSoftwareInc #NeXTCube #NeXTstation #NEXTSTEP #objectstation #ObjectiveC #OPENSTEP #PizzaBox #podcast #Postscript #Previous #Quake #Retrocomputao #Retrpolis #Rhapsody #SistemaOperacional #slab #SteveJobs #Tal

Episódio 156 – NeXT e NeXTSTEP – Parte B

https://retropolis.com.br/2024/09/11/episodio-156-parte-b/

#Podcast #AfterSTEP #AldusFreehand #AltsysVirtuoso #Apple #canon #CarnegieMellon #CERN #Cocoa #Copland #Darwin #Doom #DoomII #FVWM #GilAmelio #JohnCarmack #Linux #MacOSX #Mach #NeXT #NeXTSoftwareInc #NeXTCube #NeXTstation #NEXTSTEP #objectstation #ObjectiveC #OPENSTEP #PizzaBox #podcast #Postscript #Previous #Quake #Retrocomputao #Retrpolis #Rhapsody #SistemaOperacional #slab #SteveJobs #Tal

Episódio 156 – NeXT e NeXTSTEP – Parte B

https://retropolis.com.br/2024/09/11/episodio-156-parte-b/

#Podcast #AfterSTEP #AldusFreehand #AltsysVirtuoso #Apple #canon #CarnegieMellon #CERN #Cocoa #Copland #Darwin #Doom #DoomII #FVWM #GilAmelio #JohnCarmack #Linux #MacOSX #Mach #NeXT #NeXTSoftwareInc #NeXTCube #NeXTstation #NEXTSTEP #objectstation #ObjectiveC #OPENSTEP #PizzaBox #podcast #Postscript #Previous #Quake #Retrocomputao #Retrpolis #Rhapsody #SistemaOperacional #slab #SteveJobs #Tal

Episódio 156 – NeXT e NeXTSTEP – Parte B

https://retropolis.com.br/2024/09/11/episodio-156-parte-b/

#Podcast #AfterSTEP #AldusFreehand #AltsysVirtuoso #Apple #canon #CarnegieMellon #CERN #Cocoa #Copland #Darwin #Doom #DoomII #FVWM #GilAmelio #JohnCarmack #Linux #MacOSX #Mach #NeXT #NeXTSoftwareInc #NeXTCube #NeXTstation #NEXTSTEP #objectstation #ObjectiveC #OPENSTEP #PizzaBox #podcast #Postscript #Previous #Quake #Retrocomputao #Retrpolis #Rhapsody #SistemaOperacional #slab #SteveJobs #Tal

@BrodieOnLinux FVWM is/was great. I started using more or less when it started and I've used it as recently as 2022 on some custom embedded "carputer" type devices. Totally themeable/strippable/placeable.

Would like to see a #wayland version but... probably won't happen.

Had a stint of using #afterstep for a number of years. On an Intel Pentium dual P90 homebuilt. Ha!

#fvwm #funtimes

@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.

He told me to put that damn computer (Pentium 4) in the trash and I could not fix it.
I do not care what people think, I fixed it and installed the #antiX Linux with #fvwm window manager.

If you are a Linux user, you can work with any old computer.
Do not pay attention to what others say.
#pentium4
#fvwm
#antix

I manage files with #vifm, listen music with #ncmpcpp and watch movies with #mpv; I manage my mail with #mutt (but thinking switching to #mailx) and read documents and books with #zathura; my editor is #vim (and yes, I tried #ed the standard editor, but I felt too hardcore) and my image viewer and wallpaper setter it's #feh. I subdivide my workspace with #tmux inside multiple #xterms that sit on multiple pages of multiple desktops of my #FVWM.