On 06/02/2016 06:43 PM, David Bjergaard wrote:
Two notes: If collect-output-p is nil when run-shell-command is called, it will not wait for xrandr to finish. See: https://stumpwm.github.io/git/stumpwm-git_10.html#index-run_002dshell_002dcommand
Thanks for the comment, David. I thought I had set collect-output-p to the right values. When I need the output of xrandr, the argument is t. When all I need is the side-effect of xrandr, it is nil and the command shouldn't lock the window manager.
Today I saw Stumpwm to lock once again. No idea why, but xrandr didn't return, so I thought the explicit query for information might help and changed the xrandr call to 'xrandr -q'.
I'm glad that you are enjoying the hacking experience. All of my ideas are beyond my technical ability to execute ;)
Necessity is the mother of invention :) I just had to find a way to cope with the two monitors.
_______________________________________________ Stumpwm-devel mailing list Stumpwm-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/stumpwm-devel
