diff options
| author | Danilo M. <danix@danix.xyz> | 2026-08-15 16:20:07 +0200 |
|---|---|---|
| committer | Danilo M. <danix@danix.xyz> | 2026-08-15 16:20:07 +0200 |
| commit | 1fa8abd93fb9ada4c3dbad06a363da0b6a09e392 (patch) | |
| tree | d3e420a01a824af771d221c16a29db16b5ec41d6 /src/tagrulesdialog.h | |
| parent | 8796ed59d2410f3e47a114b6002fdefb8f259304 (diff) | |
| download | qtmaildir-1fa8abd93fb9ada4c3dbad06a363da0b6a09e392.tar.gz qtmaildir-1fa8abd93fb9ada4c3dbad06a363da0b6a09e392.zip | |
docs(backlog): specify items 91 and 92 from the user's clarifications
Both were "open, unspecified" and could not be planned from the backlog alone.
91 is not a second window. The user meant a drill-down to the selected thread
or message, the same result an `id:` query gives, reached by double-clicking
instead of typing. That removes the constraint the entry was mostly made of,
since no second QWebEngineView and no extra render process are involved, and
takes it from ? to S. What is left to decide is how the user gets back, and
that runQuery() clears the undo stack, which a gesture-triggered query would do
silently.
92 is the expensive half of the two it held: the user wants a per-message hint,
rule-written against hand-applied, and doubts its utility in the same sentence.
Nothing records that today, so it is a format change across both repos before
it is any pixels, and it stays blank on every message already tagged. Recorded
beside it is the cheaper question that may be the real one, "which rule would
tag this message", answerable from rules.json at read time with no stored
provenance and no hook change.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Diffstat (limited to 'src/tagrulesdialog.h')
0 files changed, 0 insertions, 0 deletions
