Lets have a twm(1) screen thread

This is what my twm(1) creen looks like, I tend to bounce between fvwm, vtwm, ctwm, mwm depending on my mood. Odd that neofetch(1) says I am in xwmconfig instead of twm

xclock and xload is always running and I use vdesk to simulate virtual desktops. escherknot is used for the root image.

So if you have a print of twm, toss it here. This will show what we will miss once Linux moves to 100% Wayland.

I used to use TWM occasionally, modified colours etc, but switched mainly to Fluxbox on Linux/BSD.

NetBSD 10 is using CTWM as default WM, & I quite like it, so haven't changed it.

OpenBSD uses FVWM as default, but I don't get on with it, so it's Fluxbox on there.

Originally Posted by jmccue This is what my twm(1) creen looks like

I used twm until I ran into a problem with Google Chrome. Using twm, Chrome popup menus would not stay posted. I had to switch to mwm to work around it.

My old thread here from six years or so back ...
https://www.linuxquestions.org/quest...ze-4175618143/

Nowadays I more or less just do minimal config changes, pretty much just change the title bar buttons/style to be a tab with the resize far left, iconify next to that (I don't run icon manager, just iconify/restore windows), and a close button to the right of the title

SqueezeTitle
NoDefaults
LeftTitleButton ":resize" = f.resize
LeftTitleButton ":iconify" = f.iconify
RightTitleButton ":delete" = f.delete

and increase the Menu Font size to 24

With tab style you can place them next/near to each other horizontally aligned and still have desktop space between them for activating the menu

Yes with firefox and chrome the burger bar 3 dots menu is a pain, but I tend to only use twm for windows that vnc into other systems where I run the desktop of that system once connected, for example fatdog is my main 'application server' and I run that in a kvm/qemu that uses jwm as the window manager, so chrome/firefox work fine. Which also means my wifi laptop chrome screens run at nvidia hard wired ethernet speeds. So twm is only being used at the connected 'server' level, one tab for a gui desktop, another for ssh into hashbang (wherever) for IRC, email ..etc. another running a terminal session that I use to connect to old style telnet bulletin boards such as telnet blackflag.acid.org (running export TERM=linux;export COLORTERM=linux;telnet blackflag.acid.org ... works reasonably for me for displaying the ANSI/ASCII graphics).

Dual boot laptop, Fatdog on bare metal, OpenBSD in kvm/qemu (so concurrently run), where the OpenBSD system is pretty much just base OpenBSD + tigervnc. Fatdog is a full gui desktop (chrome/libreoffice ..etc.) but that's wifi connected so slower than if I vnc into a server. USB stick I have a 17MB linux/busybox system (9MB initramfs, 7MB kernel (6.6.4)), that uses less than 60MB when operational and vnc'd into a server - where I'm running chrome/watching a youtube. Sound is forwarded via sndiod. I also have termux on my phone, so can ssh into that or scp files (photos/whatever) from that, or have it run a hotspot so my laptop can net connect via that when out/about. With termux you can even use the laptop to have the phone take a picture ... or whatever (just ssh into it and run termux-camera-photo my.jpg). Installed f-droid, then termux, and termux-api in order to be able to do that. https://wiki.termux.com/wiki/Termux:API

Not regimental about updating to the latest kernel, just do that on a as and when basis, same for busybox. The build takes less than 10 minutes to compile the kernel on my server system as the .config is highly specific to my laptop, all firmware/modules built into the kernel.

A nice thing about twm is that it doesn't conflict with other windows managers. With a thin client/multiple servers arrangement its nice being able to detach and later reattach again to continue where you left off, same as old tmux/ssh style. In a similar vein to if you run tmux locally and then ssh into another box where you also run tmux ... the multi layers of that can become confusing, nicer to run say screen locally and tmux on the server for their different (ctrl-A and ctrl-B prefix) differentials. Same for gui, twm locally, jwm/whatever on the server.

https://i.postimg.cc/MHNpgh2s/IMG-20...093924-255.jpg

My mini boot, 17MB or so mostly just linux kernel and busybox ... was originally intended as a travel system. Take the HDD out of the laptop, just travel with the laptop and usb, with just a small (<20MB) vmlinuz (build the initramfs into the kernel) single file. Just in case. Crossing some borders and you could be stopped and held/imprisoned until such times that you reveal the password to xyz file - that you may not even know what that file is/does. Eventually get to Court, don't understand the language but have it translated that you're being instructed to reveal the password, say you don't know what the file is or what the password may be ... and locked up again for another two weeks in having 'refused' before returning to Court and restarting the cycle all over again. Phones/laptop with HDD that has many files etc. can be a risk. As much a unlikely event as that situation may be for the unlucky it could be a very nasty experience, so no matter how small the risk may be its not one worth taking.