I love this repo. I've been using this script for years now but I'm not an i3 user, even when I was I used to use i3blocks as my bar.
I was thinking why it should be "i3-keyboard-layout"?
It assumes that everybody uses i3status along with i3 which is sad.
It can simply be keyboard-layout and have keyboard-layout related scripts. (kblayout for better life even)
kblayout the star, script itself.i3status-kblayout containing current i3status function of the i3-keyboard-layout.blocks-kblayout containing update script for i3blocks (something like this)
Which can be used in dwmblocks and i3blocks...
And maybe make the script read some $STATUSBAR variable before sending refresh singal to any bar so it can work with all bars (this is my implementation in my repo, default on dwmblocks):
[ "$STATUSBAR" = "i3status" ] && pgrep i3status | xargs --no-run-if-empty kill -s USR1 || # tell i3status to update
pkill -RTMIN+30 "${STATUSBAR:-dwmblocks}"
It makes the main script more aligned with its purpose: Managing layouts only.
I love this repo. I've been using this script for years now but I'm not an i3 user, even when I was I used to use i3blocks as my bar.
I was thinking why it should be "i3-keyboard-layout"?
It assumes that everybody uses i3status along with i3 which is sad.
It can simply be keyboard-layout and have keyboard-layout related scripts. (
kblayoutfor better life even)kblayoutthe star, script itself.i3status-kblayoutcontaining current i3status function of the i3-keyboard-layout.blocks-kblayoutcontaining update script for i3blocks (something like this)Which can be used in dwmblocks and i3blocks...
And maybe make the script read some
$STATUSBARvariable before sending refresh singal to any bar so it can work with all bars (this is my implementation in my repo, default ondwmblocks):It makes the main script more aligned with its purpose: Managing layouts only.