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
The idea of "interruptions" is not well documented, and breaks the log when used. Also, it seems odd that it allows you to interrupt a task with the same task. This should probably be an error, since it probably means the user doesn't know what he's doing xD
Here's what I mean:
nathan@spiral ~ % ti on hello
Start working on hello.
nathan@spiral ~ % ti interrupt hello
So you stopped working on hello.
Start working on interrupt: hello.
You are now 1 deep in interrupts.
nathan@spiral ~ % ti interrupt goodbye
So you stopped working on interrupt: hello.
Start working on interrupt: goodbye.
You are now 2 deep in interrupts.
nathan@spiral ~ % ti fin
So you stopped working on interrupt: goodbye.
Start working on interrupt: hello.
You are now 1 deep in interrupts.
nathan@spiral ~ % ti interrupt
Need the name of whatever you are working on.
1 nathan@spiral ~ % ti fin :(
So you stopped working on interrupt: hello.
Start working on hello.
Congrats, you're out of interrupts!
nathan@spiral ~ % ti fin
So you stopped working on hello.
nathan@spiral ~ % ti log
Traceback (most recent call last):
File "/home/nathan/.bin/ti", line 4, in <module>
ti.main()
File "/home/nathan/.local/lib/python3.6/site-packages/ti/__init__.py", line 451, in main
fn(**args)
File "/home/nathan/.local/lib/python3.6/site-packages/ti/__init__.py", line 265, in action_log
for name, item in sorted(log.items(), key=(lambda x: x[1]), reverse=True):
TypeError: '<' not supported between instances of 'dict' and 'dict'
I suspect the cause of the breaking log is that bash color codes are sneaking into the ti-sheet, but haven't attempted to confirm this:
The idea of "interruptions" is not well documented, and breaks the log when used. Also, it seems odd that it allows you to interrupt a task with the same task. This should probably be an error, since it probably means the user doesn't know what he's doing xD
Here's what I mean:
I suspect the cause of the breaking log is that bash color codes are sneaking into the ti-sheet, but haven't attempted to confirm this:
The text was updated successfully, but these errors were encountered: