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
Functions like mu4e-view-mark-for-trash set the mark for the message at point in the headers buffer, not for the message currently viewed in the message buffer. This behavior is a bit confusing and can lead to unwanted and unnoticeable marking of messages, e.g. if you (accidentaly) scrolled the headers buffer while reading the message (happened to me.. ;) ). Maybe mu4e-mark-at-point could be given a docid argument. Then, either a (optional) warning could pop up if the docid does not match the docid at point, or the docid argument is preferred over the docid at point (I would prefer the latter. Can't think of a reason why anyone would prefer the current behavior).
The text was updated successfully, but these errors were encountered:
Functions like mu4e-view-mark-for-trash set the mark for the message at point in the headers buffer, not for the message currently viewed in the message buffer. This behavior is a bit confusing and can lead to unwanted and unnoticeable marking of messages, e.g. if you (accidentaly) scrolled the headers buffer while reading the message (happened to me.. ;) ). Maybe mu4e-mark-at-point could be given a docid argument. Then, either a (optional) warning could pop up if the docid does not match the docid at point, or the docid argument is preferred over the docid at point (I would prefer the latter. Can't think of a reason why anyone would prefer the current behavior).
The text was updated successfully, but these errors were encountered: