Taskwarrior version: 3.4.2
Question
In task <id> info, a task's annotations are rendered twice:
- Appended as indented dated lines under the Description cell.
- Again in the bottom Date | Modification journal table (as
Annotation of '<full text>' added rows), when journal.info=1.
For a task with many annotations this produces a large duplicated block. Minimal repro:
$ task add "Example task"
$ task 1 annotate "first note"
$ task 1 annotate "second note"
$ task 1 info
The two annotations appear once under Description and again in the journal table below.
Is the under-Description rendering in info intentional? I couldn't find documentation explaining its purpose, and for tasks used as small "projects" (where annotations are a running log), the duplication is a lot of visual noise.
What I found
journal.info=0 removes the bottom journal table but keeps the under-Description annotations. There is no symmetric setting for the reverse.
indent.annotation and dateformat.annotation affect only formatting, not inclusion.
information is a static, non-modifiable report, so report.info.* does not apply.
So the two renderings are not independently controllable today.
Proposal (RFE)
Add a boolean config, e.g. annotation.info (default on for backward compatibility), that gates the under-Description annotation block in the info/information output, mirroring the existing journal.info pattern that already gates the journal table. This would let users pick either representation without losing the other.
Possibly related: #3914 (annotation indentation in reports) touches the same rendering area.
Happy to help test or take a look at the change if there is interest.
Taskwarrior version: 3.4.2
Question
In
task <id> info, a task's annotations are rendered twice:Annotation of '<full text>' addedrows), whenjournal.info=1.For a task with many annotations this produces a large duplicated block. Minimal repro:
The two annotations appear once under Description and again in the journal table below.
Is the under-Description rendering in
infointentional? I couldn't find documentation explaining its purpose, and for tasks used as small "projects" (where annotations are a running log), the duplication is a lot of visual noise.What I found
journal.info=0removes the bottom journal table but keeps the under-Description annotations. There is no symmetric setting for the reverse.indent.annotationanddateformat.annotationaffect only formatting, not inclusion.informationis a static, non-modifiable report, soreport.info.*does not apply.So the two renderings are not independently controllable today.
Proposal (RFE)
Add a boolean config, e.g.
annotation.info(defaultonfor backward compatibility), that gates the under-Description annotation block in theinfo/informationoutput, mirroring the existingjournal.infopattern that already gates the journal table. This would let users pick either representation without losing the other.Possibly related: #3914 (annotation indentation in reports) touches the same rendering area.
Happy to help test or take a look at the change if there is interest.