Differences in gamma value about autorandr HOT 6 CLOSED

I don't see how one could detect whether a change in --gamma was intentional. Always ignoring the --gamma value doesn't work either, because some users might use this intentionally.

Why is it important to you to correctly detect this? (I guess some postswitch script is in place? Would it help to report what changed to the script?)

The other thing I can think of is to give autorandr an option to generally ignore certain xrandr options, e.g.

autorandr -c --skip-options "gamma"

from autorandr.

My main issue here was that autorandr did not detect it as the same setup, although I've not (intentionally) changed it.

I am currently in the process of migrating away from gnome-settings-daemon, using awesomeWM as window manager - this might have influenced it.

At first, I thought that it was maybe some incremental counter - but currently it appears to stick.

from autorandr.

I think this gamma difference comes from using redshift.

So for me a --skip-options argument would be necessary.

from autorandr.

@phillipberndt
I've tested your branch/commit: it works as expected.
Thanks!

from autorandr.

Now it would be nice, if the system script (pm-utils/40autorandr) would read some config file (/etc/default/autorandr.conf) or something similar to allow for adjusting the command to be run:

AUTORANDR="autorandr -c --default default"

from autorandr.

Great. I pulled this to master now.

from autorandr.