* Ciprian Dorin Craciun [2015-09-16 15:22:50 +0300]:
> On Wed, Sep 16, 2015 at 2:26 PM, Michael Stapelberg wrote:
> > The recommended way is to wrap i3status as described in its manpage.
>
I'm using i3blocks without problems. Just give it a try,
On Wed, Sep 16, 2015 at 6:22 AM, Ciprian Dorin Craciun <
ciprian.crac...@gmail.com> wrote:
>
> On Wed, Sep 16, 2015 at 2:26 PM, Michael Stapelberg
wrote:
> > The recommended way is to wrap i3status as described in its manpage.
>
> The whole purpose of `i3status` is that it's
On Wed, Sep 16, 2015 at 2:22 PM, Ciprian Dorin Craciun
wrote:
> On Wed, Sep 16, 2015 at 2:26 PM, Michael Stapelberg wrote:
>> The recommended way is to wrap i3status as described in its manpage.
>
> The whole purpose of `i3status` is that it's
Ciprian Dorin Craciun writes:
> The whole purpose of `i3status` is that it's lightweight both in terms
> of resources and OS calls. Wrapping it in a script that each second
> spawns a bunch of processes just to add memory usage is counter to its
> purpose...
Just in