You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As many threads grow, and many emails keep all previous messages quoted in the current one (quoted from the start of the thread -- except in e.g. developer mailing lists), I usually remove previous emails up to the latest. In which all history is quoted below.
Now, in org-mode, emails can be kept track of using mu4e:msgid:. But if I delete earlier emails in a thread, the mu4e:msgid: link fails.
Describe the solution you'd like
Kept emails still contain the msgid of the first email referred to in org, in the References section of the raw email. It would be great to have a mu4e search taking the References.
Describe alternatives you've considered
Updating my org reference to a thread each time I delete earlier emails. Or rg <MSGID> ~/Maildir.
Additional context
None.
Thanks for comments!
The text was updated successfully, but these errors were encountered:
IDEAS.org: checked.
Is your feature request related to a problem? Please describe.
As many threads grow, and many emails keep all previous messages quoted in the current one (quoted from the start of the thread -- except in e.g. developer mailing lists), I usually remove previous emails up to the latest. In which all history is quoted below.
Now, in org-mode, emails can be kept track of using
mu4e:msgid:
. But if I delete earlier emails in a thread, themu4e:msgid:
link fails.Describe the solution you'd like
Kept emails still contain the msgid of the first email referred to in org, in the
References
section of the raw email. It would be great to have a mu4e search taking the References.Describe alternatives you've considered
Updating my org reference to a thread each time I delete earlier emails. Or
rg <MSGID> ~/Maildir
.Additional context
None.
Thanks for comments!
The text was updated successfully, but these errors were encountered: