[i3-discuss] luastatus — a universal status bar content generator supporting i3bar

[Victor Krapivensky]

Hello, i3 community! I have recently released luastatus v0.3.0 with a
lot of new stuff; hopefully somebody will find it interesting:

https://github.com/shdown/luastatus

luastatus is a universal status bar content generator. It allows the
user to configure the way the data from plugins is processed and shown,
with Lua.

Its main feature is that the content can be updated immediately as some
event occurs, be it a change of keyboard layout, active window title,
volume or a song in your favorite music player (provided that there is
a plugin for it) — a thing rather uncommon for tiling window managers.

It also avoids heavy forking, which is also a common issue of status
bar content generators, affecting performance and power consumption.

[Michael Stapelberg]

Thanks for sharing!

On Thu, Aug 2, 2018 at 5:41 AM, Victor Krapivensky <

Post by Victor Krapivensky
Hello, i3 community! I have recently released luastatus v0.3.0 with a
https://github.com/shdown/luastatus
luastatus is a universal status bar content generator. It allows the
user to configure the way the data from plugins is processed and shown,
with Lua.
Its main feature is that the content can be updated immediately as some
event occurs, be it a change of keyboard layout, active window title,
volume or a song in your favorite music player (provided that there is
a plugin for it) — a thing rather uncommon for tiling window managers.

Note that i3status also updates immediately upon receipt of a SIGUSR1
signal :)

Post by Victor Krapivensky
It also avoids heavy forking, which is also a common issue of status
bar content generators, affecting performance and power consumption.

[Jeff Abrahamson]

Post by Michael Stapelberg
Note that i3status also updates immediately upon receipt of a SIGUSR1
signal :)

That's cool.  I'm not sure what I want to do with this, but I'm sure I
want to try it. ;-)

***@birdsong:devis $ ps ax | grep i3bar
 1713 pts/25   S+     0:00 grep --color=auto i3bar
 2329 ?        S      0:00 /bin/sh -c i3bar --bar_id=bar-0
--socket="/run/user/1000/i3/ipc-socket.2187"
 2330 ?        S      0:26 i3bar --bar_id=bar-0
--socket=/run/user/1000/i3/ipc-socket.2187
***@birdsong:devis $ kill -USR1 2330
***@birdsong:devis $

And that caused i3bar to exit and some all-black windows to pop up in
the current frame.  Nothing an i3-msg restart couldn't handle, but did I
misunderstand you?

***@birdsong:~ $ i3bar --version
i3bar version 4.15 (2018-03-10) © 2010 Axel Wagner and contributors
***@birdsong:~ $  i3 --version
i3 version 4.15 (2018-03-10) © 2009 Michael Stapelberg and contributors
***@birdsong:~ $

[Johannes Lange]

You need to send SIGUSR1 to i3status, not i3bar ;-)

Cheers,
Johannes

Post by Michael Stapelberg
Note that i3status also updates immediately upon receipt of a SIGUSR1
signal :)

That's cool.  I'm not sure what I want to do with this, but I'm sure I
want to try it. ;-)
 1713 pts/25   S+     0:00 grep --color=auto i3bar
 2329 ?        S      0:00 /bin/sh -c i3bar --bar_id=bar-0
--socket="/run/user/1000/i3/ipc-socket.2187"
 2330 ?        S      0:26 i3bar --bar_id=bar-0
--socket=/run/user/1000/i3/ipc-socket.2187
And that caused i3bar to exit and some all-black windows to pop up in
the current frame.  Nothing an i3-msg restart couldn't handle, but did I
misunderstand you?
i3bar version 4.15 (2018-03-10) © 2010 Axel Wagner and contributors
i3 version 4.15 (2018-03-10) © 2009 Michael Stapelberg and contributors