Hi Andre,
here's my xrandr script. It's generated by arandr, so both screens
are set up from scratch:
=============
#!/bin/sh
xrandr --output HDMI1 --off --output LVDS1 --mode 1366x768 --pos
1280x256 --rotate normal --output DP1 --off --output VGA1 --mode
1280x1024 --pos 0x0 --rotate normal
=============
Greetings,
Levent
Am 22.01.2013 07:19, schrieb Andre Klärner:
Hi Levent,
On Tue, Jan 22, 2013 at 06:25:47AM +0100, Levent S.B. wrote:
thanks for the help. I didn't realize awesome restarts automatically when
a randr-command is executed. Still, even when i add the restart command
you proposed to my randr-script, which doesn't make sense as implied in
your mail, i need to restart awesome one more time after executing
XRandR. Well, as it's only striking mod4+crtl+r, i can live with the
bug.
well, it depends on what xrandr events are finally generated by the script.
I noticed that if I only change the primary screen (xrandr --output DP-4
--primary) that awesome didn't restart in this case.
But that is more closely written in issue #498.
Maybe post your randr-script?
Regards, Andre
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
