Sorry for the tardy reply and for being away from email for the past
few days.
In message ,
Dan Espen wrote:
>Style *Firefox EWMHDontDonateIcon, Iconoverride, Icon myfork.xpm
>
>Worked for me (with my icon).
Ye! Thank you. That seems to have worked for me too.
>Not sure if the
In message ,
Dan Espen wrote:
>>>Style *Firefox EWMHDontDonateIcon, Iconoverride, Icon myfork.xpm
>>>
>>>Worked for me (with my icon).
>>
>> Ye! Thank you. That seems to have worked for me too.
(See below. This works also for introducing an icon to represent Xterm.)
>>>When testing
In message ,
Dan Espen wrote:
>>>Sorry, for FvwmCommand to work you need this in your config:
>>>
>>>AddToFunc StartFunction I Module FvwmCommandS
OK, so now I have the following two commands added to my ~/.fvwm2rc
file and I am still gitting the same issue, i.e. a big bloated analog
xclock
In message ,
Lucio Chiappetti wrote:
>On Tue, 4 Jun 2019, Ronald F. Guilmette wrote:
>
>> Grrr. I can't imagine why this would be so hard. I didn't think
>> what I wanted to do would be so complex. Again, I just want a
>> digital xclock to appear in the blank spac
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,
In message
Jaimos Skriletz wrote:
>Style evince NoDecorHint
That's better! Thanks!
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
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, di
In message <20190605213540.hmud7pziqi64a6i5@laptop.local>,
Thomas Adam wrote:
>> For me, 3c was in fact just a blank space. I just now figured out why. On
>> FreeBSD, the xload command is in a separate package, all on its own, and that
>> package is *not* currently listed as dependency of
In message ,
Lucio Chiappetti wrote:
>As you can see fvwm is *completely* customizable (alas, at the expense of
>a learning curve, but fully worthwhile for me)
Yes, and that's terrific, at least for those who have the time to climb
the learning curve. I just don't right now, but I have
10 matches
Mail list logo
