Re: [Chromium-environment] auto-starting chromium

[Brian P. <br...@tu...>]

Yup, I was planning on that.

I could get a bit fancier:

% setenv CR_CONFIG "mywall.conf -layout 3x2 %p"
% city

Where %p would get replaced by "city + arguments", but I think
just appending the program to the end of the CR_CONFIG string
might be sufficient.


-Brian


Sean Ahern wrote:
> This sounds wonderful!
> 
> I wonder if we could expand CR_CONFIG to pass arguments to the scripts (as
> you seem to be building support for).  That way, you could do this:
> 
>     % setenv CR_CONFIG "mywall.conf -layout 3x2"
>     % city
> 
> And have the tilesorter Do The Right Thing (TM).
> 
> -Sean
> 
> Brian Paul wrote:
> 
>>I've spent the afternoon prototyping something new.  The faker
>>library now does the following:
>>
>>1. If the faker lib is able to contact the mothership, proceed normally.
>>   Otherwise...
>>
>>2. Look if the CR_CONFIG env var is set.  If so, it names a desired
>>   config file (ex: crdemo.conf)
>>
>>3. Otherwise, find the name of the running process (ex: city)
>>   Look in ~/.crconfigs for a config for city (ex: crdemo.conf)
>>
>>4. Spawn a mothership process (ex: exec("python crdemo.conf city"))
>>
>>5. The crdemo.conf file can auto-start a crserver.
>>
>>6. An atexit() handler kills the mothership when the app exits.
>>
>>
>>So, I can run city with Chromium just by typing "city <return>".
>>I have symlinks from libGL.so to libcrfaker.so.
>>
>>How does that sound for a first cut?
>>
>>-Brian
> 
> __
> sea...@ll...
> 
>