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 case you are using i3bar in hide mode: In that case i3bar will
SIGSTOP i3status anyway, when the bar isn't shown, so this won't be a
huge problem. :) If you use it in docked mode of course, you are kind of
out of luck with this.

Reply via email to