On Wed, Feb 4, 2009 at 2:19 PM, Ken Kwasnicki
<[email protected]> wrote:
> Thomas Adam wrote:
>>
>> 2009/2/4 Ken Kwasnicki <[email protected]>:
>>
>>>
>>> Hi all,
>>> I'm using fvwm 2.4.20. I have a single graphic card with TV out enabled.
>>> X is starting two displays, one on my primary screen, :0.0, and one on
>>> my TV, :0.1. So .xinitrc is run once and fvwm2 forks itself to run on
>>> the
>>> two different displays.
>>>
>>> Right now fvwm uses the same .fvwm2rc config file for both displays but
>>> I'm wondering if there is a way to get it to use a different config for
>>> my
>>> second display?
>>>
>>
>> Something like:
>>
>> fvwm -s num1 -f /path/to/config1 &
>> fvwm -s num2 -f /path/to/config2 &
>>
>> -- Thomas Adam
>>
>>
>
> Thanks Thomas and Jesús!
> I was confused because I couldn't figure out how to get fvwm to
> run twice when .xinitrc was only being once, but of course I forgot
> about using & to put the first fvwm into the background so a second
> fvwm process could start, and of course adding the -s -d -f switches
> to tell each process which display/config to use.
> It turns out it is actually important to use & on the first fvwm but not
> the second, otherwise X immediately stops after it starts. My final
> .xinitrc entries look like this:
> fvwm2 -s -d :0.0 -f .fvwm2rc &
> fvwm2 -s -d :0.1 -f .fvwm2rc.tv
>
> Works like a charm. Thank you both!
> Ken
>
> ---
> middlespot.com - see your search
>
>
>
You could use the value of DISPLAY (or any environment variable) to
conditionally load a display-specific config. Then you could keep the
things that are common to both in one file (which I'm assuming is most
of it).
Test (EnvMatch DISPLAY :0.0) Read monitor_extra_config
Test (EnvMatch DISPLAY :0.1) Read tv_extra_config
--
Thanks,
Jonathan Kotta
Hofstadter's Law:
It always takes longer than you expect, even
when you take into account Hofstadter's Law.
