On Thu, 2024-02-08 at 21:02 +1000, Stuart Longland wrote:
> On 8/2/24 13:51, hw wrote:
> > It has become a very limited option years ago and is basically
> > obsolete. Just try to run, for example, firefox on a remote host via
> > X11 forwarding. I suspect that an
On Thu, 2024-02-08 at 18:10 +, Thomas Adam wrote:
> On Thu, Feb 08, 2024 at 05:50:44AM +0100, hw wrote:
> > I still don't see why it shouldn't be possible. I never expected a
> > port, and I understand that the architectures of X11 and Wayland are
> > very differen
On Thu, 2024-02-08 at 12:38 -0800, mark_at_yahoo wrote:
> On 2/7/24 20:09, hw wrote:
> > On Sat, 2024-02-03 at 13:53 +0100, Lucio Chiappetti wrote:
> > > I hope to be able to go on with Xorg until I live.
> >
> > Or use wayland and start living now :) Living in t
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
>
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
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
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.
On Tue, 2024-01-30 at 14:02 -0700, Jaimos Skriletz wrote:
> On Tue, Jan 30, 2024 at 1:25 PM hw wrote:
> >
> > so is there finally a version that works for wayland?
> >
> No, fvwm only works with xorg and most likely won't be ported.
>
> > What are the di
Hi,
so is there finally a version that works for wayland?
What are the differences between fvwm2 and fvwm3?
Dominik Vogt writes:
> On Tue, Aug 28, 2018 at 03:22:54AM +0200, hw wrote:
> [...]
>>
>> Thanks to your other post, I finally got this:
>>
>>
>> ,
>> | [fvwm][__explain_placement]: placed new window 0x1400010 'Mozilla Firefox':
>> | in
Viktor Griph writes:
> Den mån 27 aug. 2018 00:27hw skrev:
>
>> With Firefox, I think using FixedPPosition, !UsePPosition fix it as
>> well, but the problem is that for some reason, fvwm does not place the
>> windows according to the placement policy.
>
> As you describe it it sounds as if
Dominik Vogt writes:
> On Mon, Aug 27, 2018 at 10:43:59PM +0200, hw wrote:
>> > If you use a .xinitrc you can have the WM output directed where ever
>> > you like otherwise the distro will pick a place.
>>
>> I tried that by redirecting the output of fvwm in
Dan Espen writes:
> hw writes:
>
>> Dan Espen writes:
>>
>>> hw writes:
>>>
>>>> Dominik Vogt writes:
>>>>> No, in the output of the X server, wherever that goes.
>>>>
>>>> After trying to get systemd to
Dan Espen writes:
> hw writes:
>
>> Dominik Vogt writes:
>>> No, in the output of the X server, wherever that goes.
>>
>> After trying to get systemd to create log files, it apparently goes into
>> /var/log/Xorg.0.log (where it might have gone t
Dominik Vogt writes:
> On Fri, Aug 24, 2018 at 10:58:51PM +0200, hw wrote:
>> Stefan Blachmann writes:
>> > I was annoyed and looked into that.
>> > session[re]store.js is a *horrible* mess of code, and to understand
>> > its workings, I just di
Dominik Vogt writes:
> On Thu, Aug 23, 2018 at 07:10:47PM +0200, hw wrote:
>> Hi!
>>
>> Fvwms manpage says:
>>
>>
>>Placement policy options and window stacking
>> !UsePPosition instructs fvwm to ignore the program
>&g
Stefan Blachmann writes:
> This is a long story...
> sessionrestore.js some day years ago got a regression and no longer
> did check for out-of-bounds coordinates indicating windows being
> placed on other virtual screens, i.e. it placed windows way
> off-screen, at crazy coordinates like
Hi!
Fvwms manpage says:
Placement policy options and window stacking
!UsePPosition instructs fvwm to ignore the program
specified position (PPosition hint) when adding new
windows. Using PPosition is required for some
applications,
Robert Brockway <rob...@timetraveller.org> writes:
> On Thu, 26 Apr 2018, Robert Brockway wrote:
>
>> On Thu, 26 Apr 2018, hw wrote:
>>
>>> Hi,
>>>
>>> how can I prevent fvwm from automatically switching to the desktop page
>>> wher
Michelle,
it´s so nice to see a post from you :) I remember you from the
debian-users mailing list a long time ago.
"Michelle Konzack" <linux4miche...@tamay-dogan.net> writes:
> Am DATE hackte AUTHOR in die Tasten: hw
>> Hi,
>>
>> how can I prev
Hi,
how can I prevent fvwm from automatically switching to the desktop page
where an application like gajim receives a message and activates a
window (or whatever it does to force this switch)?
As you can imagine, it´s very annoying when you´re suddenly switched to
a different program residing
21 matches
Mail list logo