You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since my screen is quite small and the number of blocklets I'd like to use is large enough, I think that it'd be nice to have a blocklet which allows to cycle through a list of different configurations of the i3blocks bar.
For instance, if the bar initially looks like (cycle through bars(disk space(battery(ddmmyyyy(clock|
clicking on the "cycle through bars" blocklet could transforms the bar to (cycle through bars(spotify(wifi(arch update(volume(keyindicator|
Clicking again could change it to some other configuration.
The most obvious way I think of in order to achieve this, is to have a blocklet which, upon click, really edits the ~/.config/i3/i3blocks by means of (the simplest think I can think of) a sed script which exploits some comment placeholders in that file.
Actually another strategy could be that ~/.config/i3/i3blocks be a symbolic link to one of the actual configuration files, and that this new blocklet simply links the link to successive configurations file in cycle. I think this would be faster, but would mean code duplication (since I could want to have the clock blocklet in every configuration).
Can I have some opinion about this?
The text was updated successfully, but these errors were encountered:
Since my screen is quite small and the number of blocklets I'd like to use is large enough, I think that it'd be nice to have a blocklet which allows to cycle through a list of different configurations of the i3blocks bar.
For instance, if the bar initially looks like
(cycle through bars(disk space(battery(ddmmyyyy(clock|
clicking on the "cycle through bars" blocklet could transforms the bar to
(cycle through bars(spotify(wifi(arch update(volume(keyindicator|
Clicking again could change it to some other configuration.
The most obvious way I think of in order to achieve this, is to have a blocklet which, upon click, really edits the
~/.config/i3/i3blocks
by means of (the simplest think I can think of) ased
script which exploits some comment placeholders in that file.Actually another strategy could be that
~/.config/i3/i3blocks
be a symbolic link to one of the actual configuration files, and that this new blocklet simply links the link to successive configurations file in cycle. I think this would be faster, but would mean code duplication (since I could want to have the clock blocklet in every configuration).Can I have some opinion about this?
The text was updated successfully, but these errors were encountered: