On Mon, Jun 20, 2011 at 07:55:51PM +0100, garbeam wrote:
> On 20 June 2011 07:48, Petr Sabata wrote:
> > On Sat, Jun 18, 2011 at 10:33:02PM +0100, garbeam wrote:
> >> On 3 June 2011 17:35, garbeam wrote:
> >> > RELOCATE
> >> > - last (google code) ??
> >> > - libixp (google code) ??
> >> > - r9p
On Mon, Jun 20, 2011 at 06:15:01PM +0100, Connor Lane Smith wrote:
> On 20 June 2011 18:05, Hiltjo Posthuma wrote:
> > getline / getdelim (re)allocates buffers though. But yes a custom
> > function with fgets would be more compatible.
I ack here.
I regularly do use getline where fgets would not su
On Mon, Jun 20, 2011 at 7:15 PM, Connor Lane Smith wrote:
>
> My point was that this is unnecessary: is your screen able to display
> more than, say, 8192 characters (a common value for BUFSIZ) on a
> single line? And even if so, why are you piping an essay into your
> status bar anyway?
>
Hah, t
On 20 June 2011 07:48, Petr Sabata wrote:
> On Sat, Jun 18, 2011 at 10:33:02PM +0100, garbeam wrote:
>> On 3 June 2011 17:35, garbeam wrote:
>> > RELOCATE
>> > - last (google code) ??
>> > - libixp (google code) ??
>> > - r9p (google code) ??
>> > - vp (google code) ??
>> > - wmii (google code) ?
A while back I put together a crappy C monitor, which I still use to the day.
Find the .c attached, compile with -lX11 as normal, peruse at will.
Cheers,
Rafa.
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#define BATTERY "BAT1"
#define BATT_
Good evening,
ilf wrote:
On 06-20 10:43, Stefan Mark wrote:
But i think think this is a better solution:
http://dwm.suckless.org/dwmstatus/
Unfortunately, this promise is not kept:
This page will give you a barebone dwmstatus project and show examples on
how to extend it to your needs.
ac
On Mon, Jun 20, 2011 at 12:07:48PM +0300, Le Tian wrote:
> On Mon, Jun 20, 2011 at 12:05 PM, Nick wrote:
>
> > On Mon, Jun 20, 2011 at 12:00:38PM +0300, Le Tian wrote:
> > > As long as "aumix -q" refuses to work after the latest update, what you
> > guys
> > > use to probe volume level? "amixer"
If were going to be linked to linux we can write a chroot like utility that
uses capabilities instead f chroot() to use it without the needs of root.
Else we can just suid that bin
On 20/06/2011, at 19:39, Connor Lane Smith wrote:
> Hey,
>
> On 20 June 2011 14:08, pancake wrote:
>> I missed
Hey,
On 20 June 2011 14:08, pancake wrote:
> I missed chroot(1)
chroot(1) isn't POSIX. We may add other, non-POSIX, utilities for the
purposes of a Linux distro (in a subdirectory), but for the moment I'd
like to concentrate on the portable tools.
> To create an archive library you need to run
On 20 June 2011 18:05, Hiltjo Posthuma wrote:
> getline / getdelim (re)allocates buffers though. But yes a custom
> function with fgets would be more compatible.
My point was that this is unnecessary: is your screen able to display
more than, say, 8192 characters (a common value for BUFSIZ) on a
On Mon, Jun 20, 2011 at 6:06 PM, Connor Lane Smith wrote:
>
> Please don't encourage things like this. getline() is available in
> POSIX 2008; though I suspect the far more portable fgets() would
> suffice.
>
getline / getdelim (re)allocates buffers though. But yes a custom
function with fgets wo
Hey,
On 20 June 2011 12:25, Kurt Van Dijck wrote:
> #ifndef _GNU_SOURCE
> #define _GNU_SOURCE
> #endif
Please don't encourage things like this. getline() is available in
POSIX 2008; though I suspect the far more portable fgets() would
suffice.
Thanks,
cls
On Mon, Jun 20, 2011 at 09:24:25AM -0400, Andrew Hills wrote:
> On Mon, Jun 20, 2011 at 8:40 AM, Kurt Van Dijck wrote:
> > I missed (and still do not see)
> > how to make xsetroot(1) read from stdin, line by line.
>
> xsetroot -name "`my_commands_that_write_to_stdout`"
>
> > That's why (I though
Thx to all for hints. I put acpi -b |tr -d ','|awk '{print $4}' onto my old
script and everythig works fine.
Maby i'll be usefull for somebody
git://github.com/dziq/configs.git
2011/6/20 Kurt Van Dijck
> On Mon, Jun 20, 2011 at 01:59:57PM +0200, ilf wrote:
> > On 06-20 13:25, Kurt Van Dijck wro
On Mon, Jun 20, 2011 at 8:40 AM, Kurt Van Dijck wrote:
> I missed (and still do not see)
> how to make xsetroot(1) read from stdin, line by line.
xsetroot -name "`my_commands_that_write_to_stdout`"
> That's why (I thought) that scripts spawn xsetroot(1) each time.
They wouldn't need to run your
I for one would be very happy about an alternative chroot
implementation, since that is missing in my base2plan9 and
base2heirloom AUR experiments (right now patching up with Busybox).
https://wiki.archlinux.org/index.php/Base2heirloom
https://wiki.archlinux.org/index.php/Base2plan9
2011/6/20 pan
I missed chroot(1) .. but after looking at the manpage I noticed that:
* all flags are long (which looks like there's no standard for those
options)
* Which flags should we handle (-u user -g group ?)
* We should chdir(path); chroot("."); instead of calling chroot(path);
- this is because the
On Mon, Jun 20, 2011 at 01:59:57PM +0200, ilf wrote:
> On 06-20 13:25, Kurt Van Dijck wrote:
> >This program allows me to put 'whatever I can create on stdout' to the
> >statusbar
>
> Euh yeah, that's what we use xsetroot(1) for.
I missed (and still do not see)
how to make xsetroot(1) read from
On 06-20 13:25, Kurt Van Dijck wrote:
This program allows me to put 'whatever I can create on stdout' to the statusbar
Euh yeah, that's what we use xsetroot(1) for.
The problem is the scripting before that setp, aquiring the "whatever I
can create on stdout".
--
ilf
Über 80 Millionen Deuts
While trying to make a custom pcf font with icons for dwm taskbar I
ultimately didn't manage to make it work under utf-8. Is there a workaround
for this problem?
--
Tian
John Carmack: "I agree with Microsoft’s assessment that WebGL is a
severe security risk. The gfx driver culture is not the culture of
security."
http://twitter.com/#!/ID_AA_Carmack/status/81732190949486592
HTML5 is great, it is the final nail in the coffin of XML, and that
can only be a good thin
On Mon, Jun 20, 2011 at 12:17:58PM +0200, Stefan Mark wrote:
> On 20.06.2011 11:59, ilf wrote:
> > On 06-19 22:55, Erik Hahn wrote:
> >> http://dwm.suckless.org/scripts/simple_monitors
> >
> > I have done this the /proc/acpi/battery/BAT0/state | shell way for years
> > and found it to be way more
On 20.06.2011 12:47, Kurt H Maier wrote:
> On Mon, Jun 20, 2011 at 5:59 AM, ilf wrote:
>> I have done this the /proc/acpi/battery/BAT0/state | shell way for years and
>> found it to be way more resource intense then calling acpi -b.
>>
>> Let's face it, the Shell/Perl/Python/whatever scripting is
On Mon, Jun 20, 2011 at 8:48 AM, Petr Sabata wrote:
>
> And why do you want to move them, actually?
Because they're garbage?
On Mon, Jun 20, 2011 at 5:01 AM, Uriel wrote:
>
> Usual garbeam fetish for busywork. He is an excellent bureaucrat.
Well, he *is* german.
--
# Kurt H Maier
On Mon, Jun 20, 2011 at 5:59 AM, ilf wrote:
> I have done this the /proc/acpi/battery/BAT0/state | shell way for years and
> found it to be way more resource intense then calling acpi -b.
>
> Let's face it, the Shell/Perl/Python/whatever scripting is relatively easy,
> but very inefficient.
I upd
On Sun, Jun 19, 2011 at 10:51:46PM +0200, Bartosz Nitkiewicz wrote:
> I'm looking for a best way to monitor battery status in dwm. Any hints?
xbattbar,
http://iplab.naist.jp/member/suguru/xbattbar.html
But no idea whether it is suckless (i.e. haven't looked beyond the surface,
which I like).
-
On 20.06.2011 11:59, ilf wrote:
> On 06-19 22:55, Erik Hahn wrote:
>> http://dwm.suckless.org/scripts/simple_monitors
>
> I have done this the /proc/acpi/battery/BAT0/state | shell way for years
> and found it to be way more resource intense then calling acpi -b.
>
> Let's face it, the Shell/Perl
On 06-19 22:55, Erik Hahn wrote:
http://dwm.suckless.org/scripts/simple_monitors
I have done this the /proc/acpi/battery/BAT0/state | shell way for years
and found it to be way more resource intense then calling acpi -b.
Let's face it, the Shell/Perl/Python/whatever scripting is relatively
On Mon, 20 Jun 2011 11:27:10 +0200
pancake wrote:
>On 06/20/11 10:24, Hadrian Węgrzynowski wrote:
>> It's maybe not the best way, but I written small utility that uses
>> Linux /proc and /sys to take stats. Original source outputs cpu
>> usage, cpu freq, cpu temp, mem usage, battery status and gp
On 06/20/11 10:24, Hadrian Węgrzynowski wrote:
On Sun, 19 Jun 2011 22:51:46 +0200
Bartosz Nitkiewicz wrote:
Hello,
I'm looking for a best way to monitor battery status in dwm. Any hints?
It's maybe not the best way, but I written small utility that uses
Linux /proc and /sys to take stats. Or
On Mon, Jun 20, 2011 at 12:05 PM, Nick wrote:
> On Mon, Jun 20, 2011 at 12:00:38PM +0300, Le Tian wrote:
> > As long as "aumix -q" refuses to work after the latest update, what you
> guys
> > use to probe volume level? "amixer" could be an alternative but it
> outputs
> > crap, that is difficult
On Mon, Jun 20, 2011 at 12:00:38PM +0300, Le Tian wrote:
> As long as "aumix -q" refuses to work after the latest update, what you guys
> use to probe volume level? "amixer" could be an alternative but it outputs
> crap, that is difficult to awk.
It isn't great, but I use 'amixer sget PCM' and awk
On Mon, Jun 20, 2011 at 8:48 AM, Petr Sabata wrote:
> On Sat, Jun 18, 2011 at 10:33:02PM +0100, garbeam wrote:
>
> I would like to hear about the status. Are things started to relocate
> > those repos?
>
> And why do you want to move them, actually?
Usual garbeam fetish for busywork. He is an e
As long as "aumix -q" refuses to work after the latest update, what you guys
use to probe volume level? "amixer" could be an alternative but it outputs
crap, that is difficult to awk.
--
Tian
On 19.06.2011 22:51, Bartosz Nitkiewicz wrote:
> Hello,
> I'm looking for a best way to monitor battery status in dwm. Any hints?
>
I use a extensible perl script
(https://svn.0mark.unserver.de/dwmd/branches/experimental/). Not
perfect, but easy to maintain and extend. The script features Monitor
On Sun, 19 Jun 2011 22:51:46 +0200
Bartosz Nitkiewicz wrote:
>Hello,
>I'm looking for a best way to monitor battery status in dwm. Any hints?
>
It's maybe not the best way, but I written small utility that uses
Linux /proc and /sys to take stats. Original source outputs cpu usage,
cpu freq, cpu
36 matches
Mail list logo
