Configurable subject response prefix #142

Closed
opened 5 months ago by oblitum · 13 comments
oblitum commented 5 months ago

I'd like to request a feature, I think very small, but that annoys me in almost all e-mail clients I've used to this day. I'd like to request for meli to have a configuration option that accepts a list of strings to be used for identifing email response prefixes. Currently when responding an email, meli prefixes the subject with "Re: ", if it's not already in the subject. The problem is, when communicating with diverse people, I often hit someone whose email client picks "RE: " for that, or even "Res: ", etc. What happens then, is that each client can't understand each other, and every subsequential email gets pilled with subject prefixes "Re: RE: Res: Re: Res: Subject", it's really annoying, I often try to evade that by manually editing the subject, but I often forget and notice the problem when it's already in my Sent folder.

I'd like to request a feature, I think very small, but that annoys me in almost all e-mail clients I've used to this day. I'd like to request for meli to have a configuration option that accepts a list of strings to be used for identifing email response prefixes. Currently when responding an email, meli prefixes the subject with "Re: ", if it's not already in the subject. The problem is, when communicating with diverse people, I often hit someone whose email client picks "RE: " for that, or even "Res: ", etc. What happens then, is that each client can't understand each other, and every subsequential email gets pilled with subject prefixes "Re: RE: Res: Re: Res: Subject", it's really annoying, I often try to evade that by manually editing the subject, but I often forget and notice the problem when it's already in my Sent folder.
Owner

Is this the solution you were thinking about?

d5594560bf

Is this the solution you were thinking about? https://git.meli.delivery/meli/meli/commit/d5594560bff45562f6c0c771dd8db8854a9354c8
Poster

Hi @epilys, that seems to be well done and should work out of the box is most cases :)

I'd like to just comment one specific person I interact with over email that has a particular interesting response prefix. Every single prefix of theirs comes with a counter, say, "RE[1]: ", "RE[2]: ", etc. I'm not sure how that should be handled, if at all.

Hi @epilys, that seems to be well done and should work out of the box is most cases :) I'd like to just comment one specific person I interact with over email that has a particular interesting response prefix. Every single prefix of theirs comes with a counter, say, "RE[1]: ", "RE[2]: ", etc. I'm not sure how that should be handled, if at all.
oblitum closed this issue 5 months ago
Poster

Oh, I think you need to proof read that string list, there's "RE:" twice, and no "Res:", only "RES: ". Seems weird.

Oh, I think you need to proof read that string list, there's "RE:" twice, and no "Res:", only "RES: ". Seems weird.
oblitum reopened this issue 5 months ago
Owner

Thanks, I'll fix that! (perils of not having compile-time hash sets)

"RE[1]: ", "RE[2]: ",

Ha! Maybe we could cook something up with the regexp pcre2 feature... Though no guarantee the stripping would happen sequentially 😄

Thanks, I'll fix that! (perils of not having compile-time hash sets) > "RE[1]: ", "RE[2]: ", Ha! Maybe we could cook something up with the regexp `pcre2` feature... Though no guarantee the stripping would happen sequentially 😄
Owner
Fixed: https://git.meli.delivery/meli/meli/commits/branch/reply-prefix
Owner

In case you want to review the diffs, I will wait a day or two before merging it into master.

In case you want to review the diffs, I will wait a day or two before merging it into master.
Poster

It seems nice, waiting for the merge to get my new build :)

It seems nice, waiting for the merge to get my new build :)
Owner

Merged!

Merged!
epilys closed this issue 5 months ago
Poster

Thanks!

Thanks!
Poster

I just realized that an original subject like "RES: something" gets mutated to "Re: something". It's nice to have Re duplication avoided, but not sure about that mutation, it'll either get flipping back and forth, or the other person's client will stack it on further responses ("RES: something" -> "Re: something" -> "RES: Re: something").

I just realized that an original subject like "RES: something" gets mutated to "Re: something". It's nice to have Re duplication avoided, but not sure about that mutation, it'll either get flipping back and forth, or the other person's client will stack it on further responses ("RES: something" -> "Re: something" -> "RES: Re: something").
Owner

Oh yeah that's true. So keep the original prefix?

Oh yeah that's true. So keep the original prefix?
epilys reopened this issue 5 months ago
Poster

I think that's the best route, leave subject as-is once prefix is identified.

I think that's the best route, leave subject as-is once prefix is identified.
Owner

Sorry for the delay, it got burried and lost in the task queue

Sorry for the delay, it got burried and lost in the task queue
epilys closed this issue 4 months ago
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Loading…
There is no content yet.