On Thu, 2007-10-25 at 16:01 +0000, Murat Güneş wrote:
> Sasa, I didn't mean "compiz --replace"; but "compiz --restart" doesn't
> seem to be documented anywhere, although effectively what it does is no
> different than "compiz --gweobrjgo4f" or just "compiz"; it just restarts
> Compiz. My point is that restarting Compiz is an (obvious) workaround.
>
though it's not always effective -- my experience has been that if
leave the computer on & go away, it can be completely unresponsive when
i return, so that i can't even type such a simple command. i suppose
you could map it to an acpi event or something.
On Thu, 2007-10-25 at 16:01 +0000, Murat Güneş wrote:
> Sasa, I didn't mean "compiz --replace"; but "compiz --restart" doesn't
> seem to be documented anywhere, although effectively what it does is no
> different than "compiz --gweobrjgo4f" or just "compiz"; it just restarts
> Compiz. My point is that restarting Compiz is an (obvious) workaround.
>
though it's not always effective -- my experience has been that if
leave the computer on & go away, it can be completely unresponsive when
i return, so that i can't even type such a simple command. i suppose
you could map it to an acpi event or something.
matt
--
Matt Price
<email address hidden>