Steve Youngs <steve@xxxxxxxx> writes:
> * Zajcev Evgeny <zevlg@xxxxxxxxx> writes:
>
> > Steve Youngs <steve@xxxxxxxx> writes:
> >> Just for kicks, I tried enabling balloon-help-mode again. So far, so
> >> good, it is behaving itself quite well.
>
> > Actually we are running kind of an experiment. There is a variable
> > `xwem-client-strict-activation' we have. Non-nil value mean the
> > client is checked to be alive, before performing activation of the
> > client. Performing activation on client that have died unexpectadely
> > may result in BadWindow X errors. And the most interesting thing -
> > `xwem-client-strict-activation' has nil value by default :)
>
> Should I test balloons with both nil and non-nil for
> `xwem-client-strict-activation'? Which should be better for balloons,
> nil or non-nil?
There is no definite for `xwem-client-strict-activation' value.
Non-nil `xwem-client-strict-activation' can save your nerves a
little, because you will have much less X errors, but it also will
strike xwem speed a little, because non-nil
`xwem-client-strict-activation' implies full interaction with X server
when activating clients.
Try them both, if you will not see the difference, set it to non-nil,
it will save your nerves :)
--
lg
|