"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
In message
Jaimos Skriletz wrote:
>Style evince NoDecorHint
That's better! Thanks!
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 fr
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 seco
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
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
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,
> x
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
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, specifical