taskwarrior-tui: description.truncated_count report column is ignored

My default report has a column with the description.truncated_count format which taskwarrior-tui does not recognize and it removes the column.

Steps to reproduce the behavior:

Modify ~/.taskrc to add description.truncated_count in your default report.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 23 (23 by maintainers)

Most upvoted comments

Thanks for opening an issue! This was on my todo list for a while now. I’ve made a new release where this should be fixed! You can find the release here: https://github.com/kdheepak/taskwarrior-tui/releases/tag/v0.9.6.

Works like a charm, thank you very much for the many fixes.

Thanks for the detailed description, I’ll look into this.

There are still several issues which I will try to describe precisely :

  1. for a terminal of width 94, with the task data imported from your json above, edit task 1 (hit m), then hit any key => crash thread 'main' panicked at 'assertion failed: self.is_char_boundary(idx)', /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/alloc/src/string.rs:1293:9
  2. for a terminal of width 94, with the task data imported from your json above, add a task with string 000000000000000000000000000000000000000000000000000000000000000000022 the description is then “truncated” to 0000000000000000000000000000000000000000000000000000000000000000000... even though it makes the description one char longer. Tip: you might want to use the unicode char which is a single char wide.
  3. it looks like there is an off by one error somewhere, see in the following screenshot, taskwarrior has a single space char between the description of task 9 and the urgency column, and taskwarrior-tui has 2 for no apparent reason. Fun fact: taskwarrior also has display bug for task 3, I guess it wrongly calculated the length of the unicode char. Selection_2021-02-04_21-19-43

I can confirm it is fixed.

Thanks for the quick fix, you rock!