Moved mails remain in *mu4e-headers*

19 views
Skip to first unread message

Phil

unread,
May 18, 2018, 6:37:33 AM5/18/18
to mu-discuss
Hi,

Just moved over to mu4e and loving it.

I have hit only one snag.  From the headers view if I mark messages for move to another folder using 'm' and the execute using 'x', the messages are moved.  That is the files in the corresponding Maildir (created using offlineimap) are physically moved, and I can see that reflected in another IMAP client - the mails are removed from the inbox, and appear in the folder I specified using 'm'.

However when I then "Jump to the maildir" and go back to my inbox, the mails still appear in the headers view.  Interestingly if I then view a message the "Maildir:" shows the correct moved folder, not the inbox.

This persists even if I quite mu4e and "M-x mu4e" again.

I'm using lastest emacs 25.3.1, and latest mu 1.1 from git.

One non-standard thing about my mu build is that I've pulled in this pending pull request (from github user titaniumbones), to stabilise HTML e-mail writing.
https://github.com/falloutphil/mu/commit/0c2fac08319177abc9b7c8921a402d1953f30441

The merge was trivial, no conflicts.


I suspect I'm just doing something dumb - could any one suggest what the expected behaviour of the headers is?


Many Thanks,

Phil.

Dirk-Jan C. Binnema

unread,
May 18, 2018, 7:03:30 AM5/18/18
to mu-di...@googlegroups.com
Perhaps you're looking at the 'related' messages?

What mu4e does by default is include "related" messages in its query
results, so a jump to inbox means "find me all messages that are in the
inbox maildir + any related ones". It's somewhat similar to what gmail
does.

If you don't want that behavior, you can set
`mu4e-headers-include-related' or toggle with 'W'.

Kind regards,
Dirk.

--
Dirk-Jan C. Binnema Helsinki, Finland
e:dj...@djcbsoftware.nl w:www.djcbsoftware.nl
pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C

Phil

unread,
May 18, 2018, 7:28:53 AM5/18/18
to mu-discuss
Of course - thanks for super quick reply!

It was a long chain and one of the old e-mails was still in the inbox, meaning that even though the later emails had been moved, they were pulled back in as related emails from the precesence of a historic e-mail.

A couple of things - I'm guessing I'd have to look into writing custom behaviour for some these, which I will look at... for now are any of the below quickly do-able?

* Is it possible only to include related messages, if the latest e-mail itself is actually in the inbox, and not just related to a historic email in the inbox?
* Is it possible to highlight e-mails that are in inbox or if highlighting is complex, perhaps adding a column to the header view so it's easy to see where messages were pulled in from?
* Is it possible to move-this-and-all-related-messages by applying a single mark?  This would ensure all emails in a chain were moved at once?


Thanks again!


Phil

unread,
May 18, 2018, 7:50:59 AM5/18/18
to mu-discuss
Actually having experiemented a bit more with the "W" toggle.  It is kinda workable as a provider of equivalent funcitonality to the 3 bullets I previously mentioned.  So it's no big deal.  They'd still be nice to have tho, if it is easy to configure any of them?



Eduardo Mercovich

unread,
May 21, 2018, 8:41:05 PM5/21/18
to mu-di...@googlegroups.com
Hi Phil.

[...]

> * Is it possible to highlight e-mails that are in inbox or if
> highlighting is complex, perhaps adding a column to the header
> view so it's easy to see where messages were pulled in from?

mu4e-headers-fields may be the setting you are looking for, or
Custom headers
(https://www.djcbsoftware.nl/code/mu/mu4e/HV-Custom-headers.html#HV-Custom-headers)
can be made to show the message location.

> * Is it possible to move-this-and-all-related-messages by
> applying a single mark? This would ensure all emails in a chain
> were moved at once?

Is is "T" (mu4e-mark-thread) useful for your usecase?

Best...


--
Eduardo Mercovich

Donde se cruzan tus talentos
con las necesidades del mundo,
ahí está tu vocación.
(Anónimo)
Reply all
Reply to author
Forward
0 new messages