Hi,
what could be the reason for fvwm showing its kill icon on startup and
when restarting?
It seems to do that since after I made some change to the configuration,
and I don't remember what that change was. When it first happened, I
thought "ok, it's been restarted like so often and might be
lee writes:
> Hi,
>
> what could be the reason for fvwm showing its kill icon on startup and
> when restarting?
Do you mean kill cursor?
> It seems to do that since after I made some change to the configuration,
> and I don't remember what that change was. When it first
Michael Großer writes:
> Michael Großer wrote:
>> Dan Espen wrote:
>>> lee writes:
>>>
Hi,
the subject pretty much says it:
Can I somehow make it so that fvwm ignores particular windows when
figuring out where to place a
elliot s writes:
> If fvwm can (be made to) optionally ignore lower layers during
> auto-placement, that would work.
Long ago, Fvwm got so many options that I'm unable to keep track.
MinOverlapPlacementPenalties has a series of arguments including "below"
that may help.
lee writes:
> Dan Espen writes:
>
>> lee writes:
>>
>>> Hi,
>>>
>>> what could be the reason for fvwm showing its kill icon on startup and
>>> when restarting?
>>
>> Do you mean kill cursor?
>
> I guess so --- it's some icon which is
Dan Espen writes:
> lee writes:
>
>> Hi,
>>
>> what could be the reason for fvwm showing its kill icon on startup and
>> when restarting?
>
> Do you mean kill cursor?
I guess so --- it's some icon which is probably supposed to look like a
skull with bones