wibox bg_image
i have found the table key bg_image in the api documention.
http://awesome.naquadah.org/doc/api/modules/wibox.html
But if I use it, with something like this:
sightbox[1] = awful.wibox({ position = bottom,
height = 32,
screen = 1
bg_image =
/path/to/image.png})
, nothing happens.
I have grep'ed the wibox library files with no hit.
Is this key still used? Or do i use it wrong?
Thx for all, mates :-)
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Vicious Fs Widget - character problem
On Mon, Jan 31, 2011 at 08:20:01PM +0100, Adrian C. wrote: On Mon, 31 Jan 2011, The Sighter wrote: vicious/helpers.lua:57: attempt to index local 'var' (a number value) Sorry I forgot about that. However i agree to you that this is a messi solution. It's not the only lua magic character... then all should be stripped. -- Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618 PGP FP: 02A5 628A D8EE 2A93 996E 929F D5CB 31B7 D20A 0618 -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org. Sorry I forgot something too. Seriously thanks for that nice widget library! :) I will search the lua docs if I have time. -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Vicious Fs Widget - character problem
On Mon, Jan 31, 2011 at 04:54:42AM +0100, Adrian C. wrote:
It's a bug with gsub usage in helpers.lua, format function. The dash -
should be escaped at the time substitution happens. Example:
foo = {/media/sam2-ntfs avail_p}
bar = 99
format = ${/media/sam2-ntfs avail_p}
print(format:gsub($ .. foo, bar))
${/media/sam2-ntfs avail_p} 0
foo = {/media/sam2%-ntfs avail_p}
print(format:gsub($ .. foo, bar))
991
What is sensible to do in the code?
format = format:gsub($ .. foo:gsub(-, %%-), bar)
...
return format
I f* hate the idea of doing that extra substitution step. Psychon help!
--
Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618
PGP FP: 02A5 628A D8EE 2A93 996E 929F D5CB 31B7 D20A 0618
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
They following code in the format function does it for me:
if type(var) == string then
var = var:gsub(-, %%-)
end
format = format:gsub($ .. var, val)
If I omit the if-clause, then there are errors like this, but i do not know in
which
case var contains a number.
vicious/helpers.lua:57: attempt to index local 'var' (a number value)
However i agree to you that this is a messi solution.
regards Sascha
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Vicious Fs Widget - character problem
Hello, I have the following problem with the fs widget.
I have a mount point called /media/sam2-ntfs
If I enter this to the format string, the variable in the widget is not
expanded correctly. You can see something like this: ${/media/sam2-ntfs used_gb}
I have tried to fix it in the fs.lua widget file, but there the mountpoint
is matched correctly. This became clear than i printed the variable m to the
logs with the following code:
if m then
io.stderr:write(m .. \n)
end
Maybe you have any ideas.
df -kP:
Filesystem 1024-blocks Used Available Capacity Mounted on
udev 10240 308 9932 4% /dev
/dev/sdb2 97656084 5420556 92235528 6% /
none 2024700 0 2024700 0% /dev/shm
/dev/sdb193307 15590 72900 18% /boot
/dev/sdb5 14650748 4205380 10445368 29% /var
/dev/sdb6 97656084 1754112 95901972 2% /home
/dev/sdb7292960332 185532128 107428204 64% /media/sam1
/dev/sdb8234372252 138207012 96165240 59% /media/sam2-ntfs
/dev/sda3262143996 71059180 191084816 28% /media/win2
/dev/sda5262143996 69416664 192727332 27% /media/win3
The relevant section in the awesome config:
fswidget_sam2_text = wibox.widget.textbox({ name = feswidget_sam2_text })
vicious.register(fswidget_sam1_text, vicious.widgets.fs,
myn.brackl .. 'span color=lightblueSam2:/span ${/media/sam2-ntfs used_gb}
| span color=white${/media/sam2-ntfs size_gb}/span' .. myn.brackr , 120)
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
add_signal() method of awesome object lost
Hello everyone. I have the following problem. If i want to add a signal to the global awesome object, like e.g. awesome.add_signal(exit, function(clienttable) io.stderr:write(Client Initiated: ) end) i get the following error: /home/sighter/.config/awesome/awconf.head.lua:23: attempt to call field 'add_signal' (a nil value) It would be nice if someone has some ideas to this problem, as i think the add_signal() method is applied to all created awesome relevant objects. With friendly breaks Sascha -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
awful.util.cycle()
Hello, I was messing around with shifty and then i see this function. Can anyone explain what it exactly does? thx greetz Sascha http://awesome.naquadah.org/doc/api/modules/awful.util.html#cycle -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: awesome 3.4.3 and shifty interactive add,del,rename not work
On Wed, Jan 27, 2010 at 03:18:51PM +0300, Ilya Martinov wrote:
On Tue, Jan 26, 2010 at 02:06:26PM -0800, Perry Hargrave wrote:
On Tue, Jan 26, 2010 at 07:45:12PM +0300, Ilya Martinov wrote:
Hi all...
Upgrade to awesome 3.4.3 and get some trouble with shifty.
If i describe tag in rc.lua everything works fine, but if i create new
tag then i can not specify tag name, it's just remains empty =(
function shifty.rename and shifty.del also do not work, and neither any
errors. xsession-errors I see.
I use shifty Version for awesome git master
http://git.mercenariesguild.net/?p=awesome.git;a=blob;f=lib/shifty.lua.in;hb=shifty-master
--
WBR...
Ilya Martinov
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
have you tried the shifty in my github repo?
http://github.com/bioe007/awesome-configs/blob/master/shifty.lua
I am using it with awesome:
v3.4-103-g81b073e (Closing In)
• Build: Jan 18 2010 10:16:39 for i686 by gcc version 4.4.2
(pe...@phargrave)
• D-Bus support: ✔
the most notably broken thing for me is that tag renaming doesnt
properly place the cursor on the taglist widget.
Unfortunately there is no reliable way of getting these widgets based on
their tag object (I tried submitting a patch for this some time ago).
I really don't feel like debugging shifty a whole lot since -next
promises to break everything all over again.
-p
now i use
awesome v3.4.3 (Engines)
• Build: Jan 20 2010 20:42:49 for i686 by gcc version 4.3.4 (r...@gibbo)
• D-Bus support: ✔
and shifty from commit:
commit from 2009-09-20 koniu shifty: and the signals... fixme :)
all work fine.
--
WBR...
Ilya Martinov
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Hi all, :-)
My solution for the problem is, to create own widgets in the rc.lua
file.
i.e. shiftyprompt[s] = widget({ type = textbox, name = shiftyprompt,
align = left })
The type has to be textbox because the function awful.prompt.run wants
a textbox widget.
Then I changed the function rename() in the shifty.lua, that it gets
a second argument which is the textbox-widget. Consequently I have to
change the function-call awful.prompt.run() in the rename-function
to provide the textboxwidget.
greetz
Sascha
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
