When selecting a message in headers view (e.g., press RETURN) the window is split and then both windows contain the message view. Switch to using mu4e-after-view-message-hook returns to correct behavior where only the newly created window from the split contains the message and the existing window continues to hold the headers view.
Don't call mu4e-update-index as this is appears to already being done and so this generates an error.
When selecting a message in headers view (e.g., press RETURN) the window is split and then both windows contain the message view. Switch to using mu4e-after-view-message-hook returns to correct behavior where only the newly created window from the split contains the message and the existing window continues to hold the headers view.
Don't call mu4e-update-index as this is appears to already being done and so this generates an error.