GothenburgBitFactory / GothenburgBitFactory/taskwarrior
[TW-1911] column width
- Dominant language
- C++
- Stars
- 6.1k
- Forks
- 423
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 11
Description
_Eric Hymowitz on 2017-05-11T14:46:41Z says:_
I don't know if this is a bug or a change.
My `.taskrc` has this defined:
{code}
report.next.columns=id,tags,due,due.remaining,description,urgency
report.next.labels=ID,Tags,Due, ,Description,U
{code}
The field "due.remaining" has a label of one space.
In taskwarrior 2.5.1, I get this result:
{code}
ID Tags Due Description U
10 home 2017-05-02 20:00 frontline cats 18
12 home 2017-05-15 16:00 4d monthly bills 8.7
2016-12-11 include wells fargo, lowes
2017-02-17 include lowes, payoff may
{code}
and the "due.remaining" column is 2 characters wide, matching the max width.
In taskwarrior 2.6.0, I get this result
{code}
ID Tags Due Description U
10 home 2017-05-02 20:00 frontline cats 18
12 home 2017-05-15 16:00 4d monthly bills 8.7
2016-12-11 include wells fargo, lowes
2017-02-17 include lowes, payoff may
{code}
and the due.remaining field is 4 characters wide -- wider than necessary.
Not a huge problem, but it changes some of the other column widths, and it bothers me aesthetically.
Contributor guide
Research direction
Start by reproducing the configured report with the shown .taskrc settings in taskwarrior 2.5.1 and 2.6.0, then trace the column-width calculation for due.remaining. Done means the field is no wider than its maximum content width and the surrounding column widths remain consistent with the expected output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100