I’ve been working on a #freebsd from scratch blog post series and was going to skip right over Xorg (preferring #wayland and #sway)…and then I heard about #NSCDE - a reimplementation of #Solaris #CDE look-and-feel via #fvwm

Thanks to work by Christian Moerz, it was a snap. Literally `pkg install Xorg nscde` a change to my .xinitrc and I was up in a pastel bliss again. Run #interlisp on it is a beautiful joy.

I was so impressed AND I got to avoid s security holes and bit rot— so I sent some librepay love. It’s a great project!

#fvwm #xquartz #macos

It is possible, via XQuartz, to run X11 applications. Here, I show xterm, but I also have firefox, etc.

All running in #fvwm

This really does make it possible to use a Mac for more than just... well, being a Mac...

#fvwm #fvwm3 version 1.1.2 has been released

For the full changelog, and release tarball, see here:

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

There are some breaking changes which are listed.

Style lines can now match some window properties:

Style (Name Foo, Class XTerm) Sticky

Would only make that window sticky if the window name matches "Foo", and the Class is "XTerm". All are case-sensitive.

There's been a few options added to existing commands' the "CursorMove" command can now take a screen name to move the cursor there.

Plus other bits-and-pieces; the changelog has more details.

If you have any issues, file a bug report on Github.

Enjoy!

One of the joys of setting up a nice #FVWM desktop is the amount of time you can use to just get one tiny toe wiggle. OK new background picked from local $HOME/.fvwm folders, but how to pick and display a bgicon from the same local config folder is a harder nut to crack. “+ "$[gt.Space]%bgicons/bg3.png%" SetBG bg3.png” #OpenBSD #RUNBSD

#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!

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.

Oh my goodness, my eyes. I'm not 15 anymore and have problems to read those really tiny fonts of #fvwm after a fresh #OpenBSD install on HiDPI screens.

IIRC there was the Ctrl+click command into the terminal window to change text size to monster-mega-huge (or something like that). But it seems to be gone. Do you have any ideas?

Hmm. I’m sure this seemed like a good idea at the time.

I’m going to be adding another two monitors. Hence it’ll be six monitors overall. I’m sure this’ll be fine. No doubt I can claim fvwm randr testing.

#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? ;) ;)

Estou processando alguns dados extraídos do #Notion via #KNIME (usando snippet de código #Python que consulta "bancos de dados do Notion" via API) e não consigo ignorar o consumo de recursos. O processador Xeon de >10 anos frita para processar cerca de mil linhas. São vários minutos até conseguir chegar numa tabela utilizável. E a coisa só não fica pior porque eu rodo um ambiente leve (baseado no #FVWM) e posso dedicar 8 GB de RAM apenas para o KNIME, já que o computador tem 40 GB.

#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

Parece que o #GNOME dobrou a aposta e ficou ainda pior. É por isso que na minha máquina principal rodo uma distro estável e um desktop “esquisito” em torno do #FVWM. A postura disruptiva e cheia de experimentos do GNOME é uma incógnita para mim. Medo de como o #Fedora #Silverblue vai ficar no mini-PC. Medo de como será o futuro com o #Wayland dominando, quando todo um mundo de possibilidades será varrido.

@pbaesse Haha, não tem problema. Valeu por ler! Sinto falta de um misto da experiência que tive usando certos aplicativos em plataformas que ficaram no passado. Queria ter uma experiência coesa, bem consistente, mas... com uma base sólida e de código aberto. Se eu tivesse os meios, financiaria o desenvolvimento, a começar pelo ambiente desktop, porque estou correndo risco de ficar órfão do #FVWM com o avanço do #Wayland (que eu estou testando com #GNOME, mas não consigo me sentir feliz usando) e, francamente, nunca tive um bom gerenciador de programas, tendo de improvisar com menus suspensos e barras de botões.