At 1242022527 time_t, koniu wrote:
The generated awesome.lua generally broke for me trying to index nil
values while settings descriptions for modules that weren't even
loaded (invaders :P) so I fiddled with the generator and added pulling
global environment + checks for the given module being
http://git.mercenariesguild.net/?p=awesome.git;a=shortlog;h=refs/heads/awful-doc
Nope, I haven't been dead or anything, on the contrary I've made some
progress with this stuff. Recent commits in the branch re-organize
some functions and make the whole thing a bit smarter.
Some of the differences
At 1241938520 time_t, koniu wrote:
Nope, I haven't been dead or anything, on the contrary I've made some
progress with this stuff. Recent commits in the branch re-organize
some functions and make the whole thing a bit smarter.
Nice.
There's more but I cant be bothered to do full changelogs
Wow man, like wow. That's really crazy stuff. Has Awesome ever been easier? No.
-AT
On Sun, May 10, 2009 at 1:32 AM, Julien Danjou jul...@danjou.info wrote:
At 1241938520 time_t, koniu wrote:
Nope, I haven't been dead or anything, on the contrary I've made some
progress with this stuff.
Work still in progress tho slowed down a bit as I'm stuck with some stuff.
I pushed some changes to:
http://git.mercenariesguild.net/?p=awesome.git;a=shortlog;h=refs/heads/awful-doc
1. cleanups - split some stuff into separate functions. There's more
to come, I'm trying to come up with sensible
At 1241713358 time_t, koniu wrote:
2. function_resolver_prompt: this doesn't quite work and I need some
expertise here.
Calling awful.help.function_resolver(awful.tag) from awesome-client or
lua prompt works nicely because awful.tag is present in global
environment. Now, if we call that
On Thu, May 7, 2009 at 19:22, Julien Danjou jul...@danjou.info wrote:
At 1241713358 time_t, koniu wrote:
Maybe add:
local env = _G
before you call module() in awful.help.
I think I've tried this and concluded that it gets environment of...
awful/init.lua.
This is not major of the problems
On Thu, May 7, 2009 at 17:22, koniu gkusni...@gmail.com wrote:
local a = loadstring(return env. .. n)() - invariably bitches about
indexing global 'env' which is nil (even tho it's not).
OK, loadstring works in global environment no matter what, so turns
out that a simple:
a =
Quick update (yay!):
Anyway here's what I've got so far - NOT QUITE READY FOR MERGING:
http://git.mercenariesguild.net/?p=awesome.git;a=shortlog;h=refs/heads/awful-doc
2. should we add shortcut descriptions to default rc.lua
I started making this and will soon push it to the branch
Wow, I must say: holy crap amazing work guys. I'm intensely impressed
with the quality of work coming out of the Awesome contributors these
days (and JD of course.)
I'm extremely proud of the window manager you guys have been putting
together, it's rapidly becoming ridiculously impressive.
Huge
On Sat, Apr 25, 2009 at 13:46, Julien Danjou jul...@danjou.info wrote:
At 1240658186 time_t, koniu wrote:
I see. Could you explain the rationale? If we where to use this, we
could as well limit it to this:
function getdata()
return data
end
Yes, that's another possibility.
There's no
Anyway, remaining questions relating to shortcut documenting:
1. where would we put the default function to display the cheatsheet?
(likely requires: awful, beautiful, naughty)
2. should we add shortcut descriptions to default rc.lua
3. what should be the default keybinding for [1].
I'm willing
Hi koniu,
At 1240471748 time_t, koniu wrote:
2.3 We can get a subset of that table by using the 'filter' argument.
Matching is done with string.find. If we set the descriptions as in
1.7, the below examples will all return the same result:
awful.doc.list( { class = something else } )
At 1240582243 time_t, koniu wrote:
I'm not 100% sure what you mean here, you didn't give an explicit
reason why it's but from what I understand you don't want the filter
function hardcoded like this. We can give possibility of supplying a
custom function like this (any better?):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julien Danjou wrote:
At 1240582243 time_t, koniu wrote:
I'm not 100% sure what you mean here, you didn't give an explicit
reason why it's but from what I understand you don't want the filter
function hardcoded like this. We can give possibility of
¡Hola chicos (¿y chicas?)!
A couple of days ago I asked jd_ if we could add an extra argument to
awful.key that would add description so we can document keybindings,
enabling awesome to display a cheatsheet. His take on that was an idea
to create a generic module to document ANY object - a very
I must say, awesome work + documentation. Sounds like a really cool
idea that opens up some possibilites. One nifty trick that this makes
somewhat easier is making Awesome modal -- press a binding to switch
your binding mode based on keybinding class. This may or may not make
sense, but it's kind
On Thu, Apr 23, 2009 at 11:21, Andrei Thorp gar...@gmail.com wrote:
somewhat easier is making Awesome modal -- press a binding to switch
your binding mode based on keybinding class. This may or may not make
sense, but it's kind of nifty-sounding as a VIM geek.
You bet it makes sense,
Also, lol:
Awesome reads the documentation for the object and figures out what to do.
-AT
On Thu, Apr 23, 2009 at 8:33 AM, koniu gkusni...@gmail.com wrote:
On Thu, Apr 23, 2009 at 11:21, Andrei Thorp gar...@gmail.com wrote:
somewhat easier is making Awesome modal -- press a binding to switch
19 matches
Mail list logo
