Pretty please, give users a choice for how Subject is handled.
DC users don’t even see the Subject. It is seen by message recipients who are using another MUA.
There are so many posts about how Subject should be handled, both here on on Github. Maybe we can’t all agree on the best way to handle the Subject, and maybe that’s not even possible or necessary, if you give users a choice in how it is handled.
There are 3 types of Subject that I can think of:
- A new email
- A reply to an email that comes from Delta Chat
- A reply to an email that comes from another MUA
If you want, you can also differentiate between emails to one address or to more than one address. This is the current behavior, though I think it unnecessary.
For each type of Subject, let the user decide what it looks like, using text and predefined fields. These fields could be
- [First few words of the message]
- [Group name]
- [Existing subject] (works only if this is a reply)
- [Prefix] – and let the user specify the prefix, such as “Chat:” If I want the subject to be [Prefix][Existing subject], then DC should check if [Existing subject] already has a prefix (whether it’s “Chat:”, “Re:”, or “Fwd:”) and remove it. This is the same behavior as most MUA’s have with the “Re:” prefix.
The current behavior is that new emails have the subject [Prefix “Chat:”][First few words of the message] if it’s to one email or [Prefix “Chat:”][Group name][First few words of the message] if it’s to more than one email. Some people (me!) might want to change this behavior.
Normies have no idea – and get weirded out by – Subject that starts with [Prefix “Chat:”][Group name]. I would much rather that my subject was just [First few words of the message] or [First few words of the message]([Group name]). That’s just me. Let users play around with how they create the Subject.
User controls how Subject is generated in different types of emails.
DC creates Subject in a pre-defined way, without user input.