Re: [ANN] Definitely Awesome - the latest news about awesome wm
Awesome Weekly is back on track! Find #13th issue here: http://definitely-awesome.posterous.com/awesome-weekly-13 -- Alexander Yakushev If or if-not. There is no try..catch-based flow control in Clojure. -- Master Joda -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: [ANN] Definitely Awesome - the latest news about awesome wm
Thank you again! -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: [ANN] Definitely Awesome - the latest news about awesome wm
Thanks, great job! On Wed, Jul 25, 2012 at 10:31 AM, Alexander Yakushev unlo...@bytopia.orgwrote: Awesome Weekly is back on track! Find #13th issue here: http://definitely-awesome.**posterous.com/awesome-weekly-**13http://definitely-awesome.posterous.com/awesome-weekly-13 -- Alexander Yakushev If or if-not. There is no try..catch-based flow control in Clojure. -- Master Joda -- To unsubscribe, send mail to awesome-unsubscribe@naquadah.**orgawesome-unsubscr...@naquadah.org .
'Shift_L + Shift_R' keybinding
Hi awesome list.
I cannot figure out a way to define a key binding to simultaneous press of
both Shifts.
if i use this, terminal starts if i press Shift_L alone
awful.key({ Shift_R, }, Shift_L,function () awful.util.spawn(terminal) end),
and if i use this than nothing happens
awful.key({ Shift_R, Shift_L} function () awful.util.spawn(terminal) end),
Any recommendations?
Thanks.
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: awesome forgets it's a tiling window manager
I could just reproduce the problem. I am using sportstracker, a Java program. To ensure it is running fine, I call wmname LG3D as a workaround. Afterward awesome behaves as I described until I restart awesome. Are there other people using wmname in the same way? Are they experiencing the same or are they not having those problems? David -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: 'Shift_L + Shift_R' keybinding
❦ 25 juillet 2012 14:25 CEST, x.pi...@gmail.com :
I cannot figure out a way to define a key binding to simultaneous press of
both Shifts.
if i use this, terminal starts if i press Shift_L alone
awful.key({ Shift_R, }, Shift_L,function () awful.util.spawn(terminal)
end),
and if i use this than nothing happens
awful.key({ Shift_R, Shift_L} function ()
awful.util.spawn(terminal) end),
I don't know if awesome can bind functions to only modifiers, but if it
cannot, you should be able to workaround the issue by providing a custom
xkb rule.
xkb_symbols lshift_rshift_terminal {
key LFSH { [ Shift_L, XF86Start ] },
key RTSH { [ Shift_R, XF86Start ] }
}
It's just a raw guess, not sure if it would work.
--
Indent to show the logical structure of a program.
- The Elements of Programming Style (Kernighan Plauger)
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
White space between widgets
Hi, I am getting white space between widgets. With the same config, I wasn't getting them earlier. Just today, I did a fresh install of my OS and copied the awesome configs which were backed up and now I am getting these white spaces http://i.imgur.com/xvr17.png My rc.lua is http://sprunge.us/IGJN So, what can be the reason? -- Regards, Abhijeet http://blog.abhijeetr.com -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
[awesome bugs] #1023 - Lets get rid of awsetbg
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1023 - Lets get rid of awsetbg User who did this - Uli Schlachter (psychon) -- @jd: The magic is in the SetCloseDownMode-request. Normally, all our windows and pixmaps get destroyed when we disconnect from the X11 server. However, we obviously want our wallpaper-pixmap to stay alive longer (so that other clients can access it via the root window property). We can't specify the lifetime of individual objects. However, the SetCloseDownMode-request allows us to say that *everything* that we created should stay alive even after we disconnect. This is why we need the new X11-connection to say that just this pixmap should stay alive. This is also why we need/should do a KillClient on the old background pixmap (if it exists), to delete the stuff that the last wallpaper-setter left behind. @Asido 1: Yeah, I don't think there are any official specs for this, but I found some description on some enlightenment web page which says the same. But I was too lazy to do the needed GetProperty requests. :-) @Asido 2: Those modes should be done in lua. Lua code should be shorter and (IMHO) more readable than the equivalent C code (and of course easier to extend). What would be the list of stuff that one would want from a wallpaper setter? Per-screen and 'global' wallpaper. Load images and use them centered (with a specified background color), rescaled to fit the whole screen, rescaled while preserving the aspect ratio, tiled. Anything I missed? The above could be done in a wallpaper lua module with functions set(lgi cairo pattern / gears.color-color), set_centered(file, screen, background color), set_tiled(file name, screen), set_maximized(file name, screen, preserve-aspect boolean). (screen can be specified as 'nil' to say 'across all screens' or 'the old awsetbg behavior'. Also, some ideas on how the default config gets changed: - The theme just gets a wallpaper or background (or sth like that) entry which just specifies a file name - The code for setting the wallpaper gets moved from beautiful into the default config, it sets the wallpaper per-screen That way people can more easily customize the wallpaper from the theme or ignore it completely. What do you think? -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1023#comment3133 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
Re: [PATCH] wallpaper.c: capability from within Awesome
On 7/24/2012 8:43 PM, Uli Schlachter wrote: If someone wants to actually set a background *image* with this, here is the nice and simple one-liner: root.wallpaper(require(lgi).cairo.Pattern.create_for_surface(require(gears.surface)(/home/psychon/Wallpaper/wp_1920.jpg))._native) do local pattern = require(lgi).cairo.Pattern.create_for_surface(require(gears.surface)(/home/psychon/Wallpaper/wp_1920.jpg)) root.wallpaper(pattern._native) end A bit longer version, but it is also a bit safer. In the oneliner above the Lua GC might spoil the fun if it kicks in right after lgi pattern object is created and before root.wallpaper() is actually called and picks up the _native value (which is lightuserdata, not holding reference to the original object). Storing Lua-side object in local variable prevents GC to collect it during the whole root.wallpaper() call. I guess that this is gotcha worth documenting in lgi docs, I will do it when I get to it :-) (With current lgi-git Pattern.create_for_surface(foo) can be shortened to Pattern(foo)) Well, not just cairo.Pattern(foo), but cairo.SurfacePattern(foo). Sorry for the nitpicking, I just wanted to have correct version in the archives ;-) pavel -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
