diff options
| author | Danilo M. <danix@danix.xyz> | 2026-08-26 17:56:05 +0200 |
|---|---|---|
| committer | Danilo M. <danix@danix.xyz> | 2026-08-26 17:56:05 +0200 |
| commit | 826a61d5ef009cac168599dc4e2b45ee8a45326d (patch) | |
| tree | 9620d0ee14d220ebf87cd106a7dcf323f3856833 /README.md | |
| parent | 9ae43f94f5d822efe582e79b47b2f5407161a38b (diff) | |
| download | qtmaildir-826a61d5ef009cac168599dc4e2b45ee8a45326d.tar.gz qtmaildir-826a61d5ef009cac168599dc4e2b45ee8a45326d.zip | |
fix: give a restored message its inbox tag back
Restore moved the file back to the inbox folder and left it invisible: the
message carried no `inbox` tag, so the Inbox view could not see it, and the
user reported restoring a message and losing it.
Delete strips `inbox` so a deleted message leaves that view, which makes
restoring it the other half of the same change. restoreResolvedMessages()
already meant to add the tag back, and the comment above the branch
describes exactly this failure, but the comparison deciding it read
`origin`, which four lines earlier had been reassigned from the bare folder
name to the finished tag. `deleted-from:Inbox` never equals `Inbox` however
an account spells its inbox, so the branch was dead and the tag never came
back.
The destination folder is taken from the move's own key instead, which is
what the surrounding code already builds and what the comment says is being
compared.
The existing test passed against this throughout. It asserted the file
moved, the origin tag came off and `deleted` came off, all of which were
true; nothing asserted the tag that decides whether the user can see the
message afterwards. It does now, and fails against the old comparison.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01P88Q3MCSCSQxKDy7pmXh9F
Diffstat (limited to 'README.md')
0 files changed, 0 insertions, 0 deletions
