Closed mattulbrich closed 1 year ago
probably related to #432.
This is an automated response. We acknowledge your report, and we appreciate your engagement. However, as there has been no recent activity in this thread, it has been marked as stale. If you have any further feedback or if the matter is still relevant, please do not hesitate to respond. Otherwise, this thread will be automatically closed in 15 days from now.
@mattulbrich can I ask you to check if this still happens in the developer preview of v2.x? It's not yet meant for productive use, so please backup your txt file. But it contains the latest alpha version of jsTodoTxt. Maybe this solves the issue at hand.
Thanks for coming back on this issue.
I downloaded sleek-2.0.0-dev3.AppImage
and the problem mentioned above does no longer arise.
Lovely, thanks for your feedback.
Closed tasks that do not have a completion date are parsed incorrectly. For instance, the task
x (A) 2023-01-01 Have a good year
should be considered completed, but it currently isn't:Apparently, same applies to tasks like
x Some task
that should be considered completed, but aren't.I assume this is due to a bug in the version of jstodotxt that is used in sleek. I was not able to reproduce the problem with 1.0.0 of that library. The original commandline tool todo.sh and other tools I use can digest this input that is within the specs.
Wanted to mention that sleek does a great job as a frontend to todo.txt
Is it an actual bug? Yes
Did you check if the bug has already been reported? Yes. Not amongst the bug reports.
Describe the bug s. above
To Reproduce Steps to reproduce the behavior:
x Closed item
)Do you see any error entries in sleeks developer tools? n/a
Expected behavior The mentioned examples should be listed as completed tasks
Screenshots s.above inline
Desktop (please complete the following information):