Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Message ID mess #135

@singularis-mzf

Description

@singularis-mzf

When a single message in inbox is selected and a new message is created, the new message will take an ID of the selected message, which causes multiple kind of wierd behaviour when the new message is sent like:

  • When the message is sent, the original message (even completely unrelated) disappers from the inbox.
  • When the selected message has multiple to-players and reply-all function has been used on it, the reply message will have the same ID as the original message which will cause conflicts in inboxes of other recipients who already have the original message there (they will not be able to select one of the messages independently).
  • And so on...

The cause is this newly added code in mail/ui/compose.lua:

if mail.selected_idxs.message[name] then
    id = mail.selected_idxs.message[name]
end

There is a code in mail.show_compose() that tries to save the id for the message, but if the id parameter is nil (which it is in most of the cases), the original id of the originally selected message is preserved. Maybe to generate a new ID in mail.show_compose() instead of waiting for a callback will help.

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugSomething isn't workingRelease blockerNo release until this is closed

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions