Re: FVWM: fvwm3?

2024-02-07 Thread hw
On Sat, 2024-02-03 at 22:05 +, Thomas Adam wrote: > [...] > GTK and QT dropping support for XLib, that's the time to worry -- as there > could, in theory, be a time when Firefox or Chromium no longer run under X > directly, without forcing a Wayland compositor. That's the real > nail-in-the-co

Re: FVWM: fvwm3?

2024-02-07 Thread hw
On Fri, 2024-02-02 at 22:42 -0600, Jason Tibbitts wrote: > I'm running wayland right now (with the KDE desktop) and can fire up > a local xterm or ssh to a different machine and run xterm and it > works just fine. Does this have to be done from an X11 client (like xterm) so you're doing it from wi

Re: FVWM: fvwm3?

2024-02-07 Thread hw
On Sat, 2024-02-03 at 13:53 +0100, Lucio Chiappetti wrote: > On Fri, 2 Feb 2024, Robert Heller wrote: > > > Afterall, no one needs more then one computer... > > I suppose there is a smiley missing after the sentence :-) > > My usual way of working (post-COVID, from home) involves usually one or

Re: FVWM: fvwm3?

2024-02-07 Thread hw
On Fri, 2024-02-02 at 10:55 -0500, Paul Fox wrote: > I realize this discussion is drifting away from fvwm, but... > > ...a major part of my daily activity has always depended on X11's > ability to function on remote displays. Does that functionality > (i.e. "DISPLAY=remotehost:0" vs. "DISPLAY=:0"

Re: FVWM: fvwm3? [on Wayland]

2024-02-07 Thread Chris Bennett
On Sun, Feb 04, 2024 at 07:30:05PM +0100, Dr. Nikolaus Klepp wrote: > Anno domini 2024 Sun, 4 Feb 01:14:21 +0100 > Martin Cermak scripsit: > > On Sun 2024-02-04 09:51 , Stuart Longland wrote: > > [...] > > > > IMHO for FVWM to survive, the FVWM community needs to focus on > > wayland. And sta