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)
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.
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
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
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
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
On 02/03/12 09:22, Uli Schlachter wrote:
On 02.03.2012 00:15, Ignas Anikevicius wrote:
Sorry, but this breaks the magic that the screen_change function is doing.
(Which I just noticed is already broken because it only handles maximized
and
fullscreen, but doesn't handle the new
On 21.02.2012 16:47, Anurag Priyam wrote:
On Mon, Feb 20, 2012 at 7:39 PM, Uli Schlachter psyc...@znc.in wrote:
On 19.02.2012 14:56, Anurag Priyam wrote:
It feels silly to return true from the callback to keygrabber.run to
keep grabbing.
[]
Pointers? I would like to change it if
On Fri, Mar 2, 2012 at 11:47 AM, Uli Schlachter psyc...@znc.in wrote:
On 21.02.2012 16:47, Anurag Priyam wrote:
[...]
Lua's C stack based API is not very intuitive (or maybe I haven't got
a hang of it yet). Hope I have got it right. The patch does seem to
work here.
This patch broke
On 02.03.2012 18:47, Anurag Priyam wrote:
On Fri, Mar 2, 2012 at 11:47 AM, Uli Schlachter psyc...@znc.in wrote:
On 21.02.2012 16:47, Anurag Priyam wrote:
[...]
Lua's C stack based API is not very intuitive (or maybe I haven't got
a hang of it yet). Hope I have got it right. The patch does
10 matches
Mail list logo
