29 lines
1.5 KiB
Markdown
29 lines
1.5 KiB
Markdown
# A selection of information output tools for dmenu
|
|
|
|
These are a selection of independant tools for displaying various information
|
|
about system status in dmenu. Some of them i.e. `volume` have options (up, down, mute...)
|
|
which are selectable options in dmenu.
|
|
|
|
<video controls>
|
|
<source src="https://notnull.click/media/5e8bf5dd30ac7b777edb99506539488a1a90da7d9e28fd98cef76a6193474a67.mp4" type="video/mp4">
|
|
<p>Your browser doesn't support HTML5 video. Here is a <a href="https://notnull.click/media/5e8bf5dd30ac7b777edb99506539488a1a90da7d9e28fd98cef76a6193474a67.mp4">link to the video</a> instead.</p>
|
|
</video>
|
|
|
|
They are compiled separately, for example:
|
|
```nim
|
|
nim c pingclock
|
|
```
|
|
and then run with
|
|
```sh
|
|
./pingclock dmenu
|
|
or
|
|
./pingclock rofi
|
|
```
|
|
it can also be run without any arguments to receive a i3bar compatible json string
|
|
|
|
Personally, I have these bound to key combinations in i3. In fact, I have a seperate `bindsym` mode in which all these tools are accessible i.e. `$mod+i` to get to "info" mode then `p` to show pingclock.
|
|
There's also an i3bar_tools_threaded folder with tools for use with i3bar/i3blocks which continously update. Currently these are not working as I recently switched from this as primary, to a secondary choice.
|
|
|
|
These have some configuration variables explicit to me, you'll need to change them for you for them to be useful I imagine.
|
|
|
|
I'm aware my code is messy. I'm aware my code is undocumented. But hopefully these things are simple enough to work out.
|