[Nix-dev] wmii and xrandr

[Nicolas Pierron]

On Thu, Mar 12, 2009 at 23:14, Marc Weber <marco-oweber at gmx.de> wrote:
>> The goal of the waitPID variable is to wait in order to end the
>> session when a job terminate.  By adding this loop you kill extra
>> configuration which could be loaded after and force the user to quit
>> with a bad method.
>>
>> I am against this method,  you should use the waitPID variable with a
>> primary job which allow user to quit properly and to resize the
>> screen.
>>
>> So I foresee two possible solutions to this problem:
>> - patching wmii
>> - adding a wrapper which handle wmii restart and the screen resize
>> without leaving the PID number.
>
> I don't want to spend much time on patching it. Better to say I can't.
> Is there a way to make this "bad" loop optional?

I prefer not, to keep things clean.

> eg
> wmii = {
>  enableBadHackishSimpleWorkingForeverRestartLoop = true;
> }
>
> Then it wouldn't be default ( I don't know the default way to exit wmii

wmiir xwrite /ctl quit

> properly anyway.. I never switch .. ) and I'd be happy because I could
> just use the hacky way which I already know to be working without much
> testing or rebuilding etc..
> I won't harm anyone stepping in fixing this properly. :)

Yes, but we should avoid to commit hacky stuff as long as this is not
a primary issue for most of the users.

-- 
Nicolas Pierron
http://www.linkedin.com/in/nicolasbpierron
- If you are doing something twice then you should try to do it once.