On Fri, Jan 14, 2022 at 03:26:36AM +0100, Vincent Lefevre wrote:
I strongly disagree with the addition of $reply_prefix
(commit 9c1ce59874ce1c8e97d0c5bd71847596dafb1d50), as this is
contrary to RFC 5322, and non-standard prefixes are annoying
in practice and not necessarily recognized by other users.

Why strongly against? $reply_regexp has had "aw" listed for years (although I just took that out of the default value too...).

I've been told other prefixes are often used in some lists, and the practice is getting more common. Why not give users the option to adjust it, if they deem it appropriate, for some lists?

I'm willing to back the change out, but Mutt also gives the option for crazy things like $indent_string. I don't think by giving the option I'm *encouraging* it, but it does make it easier to adjust if they want.

--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA

Attachment: signature.asc
Description: PGP signature

Reply via email to