xset not working on session start

[Glynn Clements]

Atom Smasher wrote:

> the xset commands are successfully executed, first from ~/.xsession then 
> by ~/.e16/Start/xset.sh. when i open a terminal and type 'xset q' i 
> *usually* don't see the settings i want.
> 
> i tried adding:
>  	xterm -e 'sleep 4 ; xset q ; cat' &
> to the config files, and *usually* saw the wrong settings. if i left out 
> the sleep command i always saw the correct settings, even if they reverted 
> to the wrong settings a few seconds later.
> 
> if i copy and paste the xset command(s) in an interactive shell, it seems 
> to work as expected every time.

IOW, something else is changing the settings. In which case, you have
three options:

1. Figure out what is changing the settings, and disable it.

2. Figure out what is changing the settings, and configure it to use
your preferred settings (thus eliminating the need to use xset).

3. Add a delay before the xset commands so that they get executed
*after* whatever else is changing the settings. For this, you'll need
to use a background subshell, e.g.:

(
	sleep 10
	xset b 100 440 101 && echo 'bell set'
	xset m 4/1 8  && echo 'mouse set'
	xset dpms 0 0 0 && echo 'dpms set'
) &

If you don't do this in the background, you'll probably end up
delaying the "other thing" as well, which would defeat the purpose.

-- 
Glynn Clements <glynn at gclements.plus.com>