I3status-rust: Block request: Taskwarrior
It would be cool to have a taskwarrior block that indicates the current status of your tasks, something like X ready tasks, Y nearly due tasks, Z overdue tasks.
I'd be willing to implement this, but it's not that far up my todo list yet, so if someone else want to do it first, feel free!
jcgruenhage
All 15 comments
It's probably possible to do this with the Custom block already. I've been a bit hesitant to add support for todo managers in the past (see #195), since none of them seem to have particularly widespread adoption. But others may disagree.
atheriel
on 9 Dec 2018
If it's behind a feature flag I don't see the harm in it though
jcgruenhage
on 9 Dec 2018
We only need to use a feature flag if the block introduces external crate dependencies -- is that what you had in mind?
atheriel
on 9 Dec 2018
I already have simple taskwarrior block for personal use here: https://github.com/jubnzv/i3status-rust/commit/6dc80849a4270ccf76a0540e9cf512b832efc585. It's implemented as a wrapper around task command (following these guidelines), so it may be cleaner to use Custom block instead. Something like:
[[block]]
block = "custom"
command = "echo  `task rc.gc=off sched.before:today+1d -COMPLETED -DELETED -DUETODAY count`"
interval = 60
If it can be useful for someone else, I could extend my wrapper functionality in separate crate and create PR with a new block. Any thoughts?
jubnzv
on 17 Mar 2019
I tend to think that if a block is simply displaying the output of a shell command every minute, there is not much advantage to a "native" block over using the custom block, as you have in your example.
atheriel
on 18 Mar 2019
Can custom blocks do colors? I'd like to have the block red when tasks are overdue, yellow when there's still things due soon or scheduled for today and plain gray otherwise.
jcgruenhage
on 18 Mar 2019
Yep! Semantically meaningful colours would be one good reason to use a native block. Adding colour to the count from a shell command is exactly what the Pacman block does, for example.
atheriel
on 18 Mar 2019
How about enabling pango markup for the various widgets (button, text, etc)? Then should be able to add colour to any custom block with just the shell output.
ammgws
on 18 Mar 2019
@ammgws Oh, that's a good point. Have I missed an open issue/PR for this?
atheriel
on 19 Mar 2019
I had a PR merged for the separator block, leaving the other blocks for later since I wanted to test it first. I can open one if the test proves promising.
ammgws
on 19 Mar 2019
Seems to work fine so I'll open a PR.
ammgws
on 19 Mar 2019
That is just the text color, not the block color though, right?
jcgruenhage
on 24 Mar 2019
You can set the block colour too. See the second image in #346
ammgws
on 24 Mar 2019
That is the text background colour, not the block colour.
jcgruenhage
on 24 Mar 2019
Implemented via #600
ammgws
on 22 Apr 2020
Related issues
jpeeler
·
5Comments
concatime
·
4Comments
yawpitch
·
4Comments
lovesegfault
·
7Comments
marvin-steinke
·
4Comments
Most helpful comment
I tend to think that if a block is simply displaying the output of a shell command every minute, there is not much advantage to a "native" block over using the custom block, as you have in your example.