BTW I'm using awesome 3.4.10 with obvious 3.4.10 on Arch without much
trouble. Here is my configuration related to the widget you're
interested:
-- Choose one type and comment out another
-- CPU usage widget (textbox)
cpuwidget = widget({ type = 'textbox' })
vicious.register(cpuwidget, vicious.widgets.cpu, '$1%')
-- CPU usage widget (graph)
cpuwidget = awful.widget.graph()
cpuwidget:set_width(60)
cpuwidget:set_height(30)
cpuwidget:set_background_color('#494B4F')
cpuwidget:set_color('#FF5656')
cpuwidget:set_gradient_colors({ '#FF5656', '#88A175', '#AECF96' })
vicious.register(cpuwidget, vicious.widgets.cpu, '$1')
volumewidget =
obvious.volume_alsa():set_layout(awful.widget.layout.horizontal.rightleft).widget
mywibox[s].widgets = {
cpuwidget.widget,
separator,
volumewidget
}
On Wed, Oct 26, 2011 at 4:58 AM, Thorsten Sperber <[email protected]> wrote:
> On 19.10.2011 11:52, Thorsten Sperber wrote:
>> On 19.10.2011 10:57, Uli Schlachter wrote:
>>>
>>> Hi,
>>>
>>> I haven't come up with any good idea yet, so:
>>>
>>> Anything on awesome's stderr? Assuming you use linux, 'ls -l
>>> /proc/$(pidof
>>> awesome)/fd/2' will tell you where awesome's stderr goes to.
>>>
>> Nope, no output in both systems. I always have a xterm open with tail
>> -f $log, because I'm continously doing stupid syntax errors in lua ;D
>>
>>
>>
>
> two weeks, no response, no further ideas? Isn't there really anyone
> using this? I can't debug something which doesnt write any error on
> stdout/stderr.
>
> Thorsten
>
>
> --
> To unsubscribe, send mail to [email protected].
>
--
Rainux Luo
--
To unsubscribe, send mail to [email protected].
