2012/3/3 Uli Schlachter
> On 03.03.2012 22:40, Raphael Fournier wrote:
> > (to the devs: is it really the expected behavior, to have the terms stay
> on
> > a screen, even if its numbers goes from 1 to 2 ?)
>
> WHICH MERE MORTAL DARES TO SUMMON THE ALMIGHTY DEV? *insert evil laughter*
> Let's s
> diff rc.dualhead rc.singlehead
>
> 399c399
> < properties = { tag = tags[2][8] } },
Don't do this. Just use screen.count() instead of hard coded screen ID
in a single rc.lua. It will return 1 to you with one screen and 2 with
two screens.
--
Adrian C. (anrxc) | anrxc..sysphere.org
On 03.03.2012 22:40, Raphael Fournier wrote:
> (to the devs: is it really the expected behavior, to have the terms stay on
> a screen, even if its numbers goes from 1 to 2 ?)
WHICH MERE MORTAL DARES TO SUMMON THE ALMIGHTY DEV? *insert evil laughter*
Let's see...
Function scan() in awesome.c look
I will also try screenful sounds very promising. A little typo in the
README (No -> Now).
Perhaps you could add it to the wiki (at least make a link to github), it
may help other awesome users !
Thanks !
And, indeed, thanks to others for their solutions (I may also try the
sharedtags solution).
(
Excerpts from Dariusz Luksza's message of Fri Mar 02 20:20:57 +0100 2012:
> You can try screenful, it will automatically discover connected monitors and
> setup proper arrangement based on configuration
>
> [1] https://github.com/dluksza/screenful
Thank you soo much, seriously. \o/
--
Regards,
On 03/02/12 22:01, kevinrong wrote:
before you switch to dual monitor, enter a2, before you switch back to laptop
only, enter a1.
using screenful you don't need to copy anything, it will "automatically" detect
that external
screen was connected/disconnected and launch proper xrandr configurat
I use this method. it's not perfect but works for me.
have two rc config in ~/.config/awesome, one is rc.dualhead (for two
monitor), one is rc.singlehead. the only difference is for dual head, you
can specify Class/Name application been put in tags[2][x]. [2] is the
second monitor.
diff rc.dualhe
On 03/02/12 17:42, Gabriel Lecouvreur wrote:
Hello,
I have a small issue with awesome : I sometimes plug my laptop to an external
screen and then issue an xrandr command to make the new screen available. Then,
Awesome restarts. And I am not pleased with the way it deals with clients :
clients w
My external monitor is already set as primary (at least it is screen 1
for awesome). But my urxvts act as if they are stuck on the laptop
screen (as if there tag table contain screen.count instead of "1").
Yes, I could also disable the laptop screen but I like to keep a root
term there and a few o
What if you set the extern monitor as primary? I usually set my HDMI
output as primary, sometimes I even disable my laptop monitor.
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Hello,
I have a small issue with awesome : I sometimes plug my laptop to an
external
screen and then issue an xrandr command to make the new screen available.
Then,
Awesome restarts. And I am not pleased with the way it deals with clients :
clients with no rule in my rc.lua (like my urxvt-terms)
11 matches
Mail list logo
