Am 24.03.2011 15:38, schrieb Thorsten Sperber:
> I don't know, what causes the margin
I could reproduce it now by clicking a link in another program (pidgin
in this case).
- open a (firefox) window in a tag with float layout
- maximize it
- move to another tag
- click a link
- switch to the brows
What I did with browser was:
1. added a rule to make browser window float (tag has nonfloat layout)
2. added a callback that checks screen size, and height of wibox and sets
proper dimensions to the browser window
I didn't maximize the window, because that caused problems with fullscreen
Am 24.03.2011 15:38, schrieb Thorsten Sperber:
> I don't know, what causes the margin
I could reproduce it now by clicking a link in another program (pidgin
in this case).
- open a (firefox) window in a tag with float layout
- maximize it
- move to another tag
- click a link
- switch to the brows
Hi,
I have a problem with an unwanted margin above maximized windows in
float layout. tag #2 is my "browser" tag and has float as layout, but
the browser windows are maximized as default (I switched the tag to
float after I realized that I couldn't open small xterms on max* layout).
I don't know,
what if my function or whatever i want to send to awesome-client. does
awesome-client now support something like #/usr/bin/awesome-client?
2010/12/17 Vivian Brégier
> For your information, using "tr" instead of "xargs echo" should remove
> the string size limit, since the string isn't passed as
