Re: FVWM: Two small oddities
On Fri, Jun 07, 2019 at 10:31:56PM -0700, Ronald F. Guilmette wrote: > > I've just noticed a couple of very odd things whilst trying to use various > applications under fvwm on FreeBSD, and I thought that rather than just > ignoring these, I should perhaps say something, in case they turn out to > be actual bugs. > > 1) > > First, under fvwm, some certain applications, specifically evince and > the chromium browser, display with any of the usual outer framing that > fvwm seems to provide for all other X application programs, e.g. Xterm, > xpdf, and the Firefox and Oprera browsers. > > I made an effort to see if these two applications (evince & chromium) > exhibit the same issue when run under twm. They do not, in that case. > When run under twm, they get an outer frame just like everything else. Chrome has an option under settings called "Use system title bar and borders". Turn it on an it works fine. Evince is a problem. "Science advances one funeral at a time." - Max Planck E. Frank Ball III
Re: FVWM: Two small oddities
On Sat, Jun 8, 2019 at 5:59 AM Thomas Adam wrote: > > On Fri, Jun 07, 2019 at 10:31:56PM -0700, Ronald F. Guilmette wrote: > > 1) > > > > First, under fvwm, some certain applications, specifically evince and > > the chromium browser, display with any of the usual outer framing that > > fvwm seems to provide for all other X application programs, e.g. Xterm, > > xpdf, and the Firefox and Oprera browsers. > > Chromium has an option to disable this. > You may need to restart chromium after you change this setting. > As for evince and others, this is due to CSD (Client-side Decorations). > There's no proper way around this other than to use a patched gtk which uses > LD_PRELOAD to override this behaviour. > You can tell fvwm to ignore the decor hints caused by the CSD to turn off the decor. For me the following works to put borders/titlebar on evince. Style evince NoDecorHint This may have other affects that all decor hints are ignored. For my use it works in allowing fvwm to decorate my evince windows. Though I personally just like the border, and not the titlebar on my evince windows (since it dose provided maximum and minimum buttons on the CSD), so I use Style evince NoDecorHint, !Title > Have a look at gtk3-nocsd (https://github.com/PCMan/gtk3-nocsd). I've just > checekd my FreeBSD machine -- it's not packaged. > This option is also available if there are other decor hints you want honored and ignoring them all with the above style isn't appropriate for your use case. jaimos
Re: FVWM: Two small oddities
On Fri, Jun 07, 2019 at 10:31:56PM -0700, Ronald F. Guilmette wrote: > 1) > > First, under fvwm, some certain applications, specifically evince and > the chromium browser, display with any of the usual outer framing that > fvwm seems to provide for all other X application programs, e.g. Xterm, > xpdf, and the Firefox and Oprera browsers. Chromium has an option to disable this. As for evince and others, this is due to CSD (Client-side Decorations). There's no proper way around this other than to use a patched gtk which uses LD_PRELOAD to override this behaviour. Have a look at gtk3-nocsd (https://github.com/PCMan/gtk3-nocsd). I've just checekd my FreeBSD machine -- it's not packaged. -- Thomas Adam
Re: FVWM: Two small oddities
In message Jaimos Skriletz wrote: >Style evince NoDecorHint That's better! Thanks!
Re: FVWM: Two small oddities
On Sat, Jun 08, 2019 at 12:58:21PM +0100, Thomas Adam wrote: > On Fri, Jun 07, 2019 at 10:31:56PM -0700, Ronald F. Guilmette wrote: > > 1) > > > > First, under fvwm, some certain applications, specifically evince and > > the chromium browser, display with any of the usual outer framing that > > fvwm seems to provide for all other X application programs, e.g. Xterm, > > xpdf, and the Firefox and Oprera browsers. > > Chromium has an option to disable this. > > As for evince and others, this is due to CSD (Client-side Decorations). > There's no proper way around this other than to use a patched gtk which uses > LD_PRELOAD to override this behaviour. > > Have a look at gtk3-nocsd (https://github.com/PCMan/gtk3-nocsd). I've just > checekd my FreeBSD machine -- it's not packaged. > > -- Thomas Adam gtk3-nocsd is packaged for Ubuntu 18.04 & Debian 9. "gtk3-nocsd evince" works great. Thank you. "Science advances one funeral at a time." - Max Planck E. Frank Ball III
Re: FVWM: Two small oddities
In message <20190608060220.gf4...@kamajii.efball.com>,
E Frank Ball wrote:
>Chrome has an option under settings called "Use system title bar and
>borders". Turn it on an it works fine. Evince is a problem.
OK. Thanks. You're right. That enables the normative borders.
What about the second issue I mentioned? That one is far more serious.
Why doesn't chrome{ium} behave itself in a normal fashion, just like
everything else, and pop to the foreground when you click on some visible
part of it (e.g. along the very top edge on the window)?
I freely admit that I know almost nothing about X generally, and/or
about X window managers, but it seems *really* bizzare to me that
chrom{ium} is even able to "opt out" of this foregrounding behavior...
behavior which every other type of application window seems to do
effortlessly, and in a "standard" fashion.
So, is there a chrome setting for this too?
Isn't fvwm the thing that should be bringing the window to the foreground?
Re: FVWM: Two small oddities
In message <20190608115819.sbfwisfzxd4xxecg@laptop.local>, Thomas Adam wrote: >On Fri, Jun 07, 2019 at 10:31:56PM -0700, Ronald F. Guilmette wrote: >> 1) >> >> First, under fvwm, some certain applications, specifically evince and >> the chromium browser, display with any of the usual outer framing that >> fvwm seems to provide for all other X application programs, e.g. Xterm, >> xpdf, and the Firefox and Oprera browsers. > >Chromium has an option to disable this. Yes. Thanks. >As for evince and others, this is due to CSD (Client-side Decorations). >There's no proper way around this other than to use a patched gtk which uses >LD_PRELOAD to override this behaviour. > >Have a look at gtk3-nocsd (https://github.com/PCMan/gtk3-nocsd). I've just >checekd my FreeBSD machine -- it's not packaged. Oh, vey! I'm reading the README file, which is about as much as I am likely to do. Even just from the README file I can see that this is a seriously messed up situation. Maybe the GTK folks should have checked with a few more people before going of on their own private tangent. Fortunately, in my case, evince seems to be the one and only tool that I'm likely to use that has this issue. So I guess I'll just learn to live with it in that one case.
Re: FVWM: Two small oddities
"Ronald F. Guilmette" writes:
> In message <20190608060220.gf4...@kamajii.efball.com>,
> E Frank Ball wrote:
>
>>Chrome has an option under settings called "Use system title bar and
>>borders". Turn it on an it works fine. Evince is a problem.
>
> OK. Thanks. You're right. That enables the normative borders.
>
> What about the second issue I mentioned? That one is far more serious.
> Why doesn't chrome{ium} behave itself in a normal fashion, just like
> everything else, and pop to the foreground when you click on some visible
> part of it (e.g. along the very top edge on the window)?
>
> I freely admit that I know almost nothing about X generally, and/or
> about X window managers, but it seems *really* bizzare to me that
> chrom{ium} is even able to "opt out" of this foregrounding behavior...
> behavior which every other type of application window seems to do
> effortlessly, and in a "standard" fashion.
>
> So, is there a chrome setting for this too?
>
> Isn't fvwm the thing that should be bringing the window to the foreground?
In typical Fvwm fashion, Fvwm does very little if you don't tell it to.
This is for people like me that want total control.
You might like:
Style * MouseFocusClickRaises
If you search the man page for "raise" you'll soon realize, there are
lots of options.
Personally, I bind a key to raise and bind a title bar click to raise.
--
Dan Espen
