Re: $reply_prefix

2022-01-14 Thread Jean Louis
* Vincent Lefevre [2022-01-14 12:20]: > On 2022-01-14 11:05:14 +0300, Jean Louis wrote: > > I do not see anything that is "against" the RFC5322. > > You misread it. See my other replies. > > > It MAY, and it MAY NOT. There is no strict rule to it. > > Indeed, it doesn't say "MAY NOT", so that

Re: $reply_prefix

2022-01-14 Thread Jean Louis
* Tapani Tarvainen [2022-01-14 10:20]: > On Thu, Jan 13, 2022 at 08:20:55PM -0800, Kevin J. McCarthy (ke...@8t8.us) > wrote: > > > I've been told other prefixes are often used in some lists, and the > > practice is getting more common. > > Other prefixes have also long been used by some

Re: $reply_prefix

2022-01-14 Thread Vincent Lefevre
On 2022-01-13 19:41:12 -0800, Will Yardley wrote: > On Thu, Jan 13, 2022 at 09:42:27PM -0500, John Hawkinson wrote: > > Although my personal preference is that this is not a knob Mutt needs, > > I am cognizant that some other popular MUAs use "RE: " rather than > > "Re: " and while that looks

Re: $reply_prefix

2022-01-14 Thread Vincent Lefevre
On 2022-01-13 21:25:27 -0800, Kevin J. McCarthy wrote: > On Thu, Jan 13, 2022 at 11:57:37PM -0500, John Hawkinson wrote: > > One is confined to the content of a message and the other affects > > critical message metadata that is often displayed in abbreviated form. > > "Critical message metadata"

Re: $reply_prefix

2022-01-14 Thread Vincent Lefevre
On 2022-01-14 11:05:14 +0300, Jean Louis wrote: > I do not see anything that is "against" the RFC5322. You misread it. See my other replies. > It MAY, and it MAY NOT. There is no strict rule to it. Indeed, it doesn't say "MAY NOT", so that "Re: " is not forbidden. But this does not mean that

Re: $reply_prefix

2022-01-14 Thread Vincent Lefevre
On 2022-01-14 09:49:12 +0100, Fredrik Gustafsson wrote: > That's already the case. For example in Sweden, "Sv:" is used instead of > "Re:". This is not a mutt decision and > the decision is already made for us. We can like it or dislike it. Fortunately most people do not use it. In my mail

Re: $reply_prefix

2022-01-14 Thread Fredrik Gustafsson
Den fre 14 jan. 2022 kl 09:38 skrev Vincent Lefevre : > Imagine that any language (including those in a non-Latin script) > would like to use its own reply prefix, and the complexity to handle > that... > That's already the case. For example in Sweden, "Sv:" is used instead of "Re:". This is not

Re: $reply_prefix

2022-01-14 Thread Vincent Lefevre
On 2022-01-14 09:10:19 +0200, Tapani Tarvainen wrote: > On Thu, Jan 13, 2022 at 08:20:55PM -0800, Kevin J. McCarthy (ke...@8t8.us) > wrote: > > > I've been told other prefixes are often used in some lists, and the > > practice is getting more common. > > Other prefixes have also long been used

Re: Mutt on ubuntu 20

2022-01-14 Thread Derek Martin
On Fri, Jan 14, 2022 at 03:19:39AM +0100, Vincent Lefevre wrote: > On 2022-01-13 15:36:04 -0600, Derek Martin wrote: > > So... The only difference between this and hdrdefault is that > > hdrdefault's order does not matter. This is a very minor difference, > > and the distinction disappears so

Re: $reply_prefix

2022-01-14 Thread Eike Rathke
Hi, On Friday, 2022-01-14 14:36:13 +0300, Jean Louis wrote: > > > It MAY, and it MAY NOT. There is no strict rule to it. > > > > Indeed, it doesn't say "MAY NOT", so that "Re: " is not forbidden. > > But this does not mean that other prefixes are allowed. > > Quite contrary, my understanding

Re: $reply_prefix

2022-01-14 Thread Derek Martin
On Fri, Jan 14, 2022 at 09:37:06AM +0100, Vincent Lefevre wrote: > On 2022-01-13 19:41:12 -0800, Will Yardley wrote: > > On Thu, Jan 13, 2022 at 09:42:27PM -0500, John Hawkinson wrote: > > > Perhaps language from RFC5322 Sec. 3.6.5 should be imported into the > > > documentation for $reply_prefix,

Re: $reply_prefix

2022-01-14 Thread Derek Martin
On Fri, Jan 14, 2022 at 04:27:10PM -0600, Derek Martin wrote: > On Thu, Jan 13, 2022 at 09:25:27PM -0800, Kevin J. McCarthy wrote: > > On Thu, Jan 13, 2022 at 11:57:37PM -0500, John Hawkinson wrote: > > > Kevin J. McCarthy wrote on Thu, 13 Jan 2022 > > > at 23:20:55 EST in : > > > > > > > I've

Re: $reply_prefix

2022-01-14 Thread Derek Martin
On Thu, Jan 13, 2022 at 09:25:27PM -0800, Kevin J. McCarthy wrote: > On Thu, Jan 13, 2022 at 11:57:37PM -0500, John Hawkinson wrote: > > Kevin J. McCarthy wrote on Thu, 13 Jan 2022 > > at 23:20:55 EST in : > > > > > I've been told other prefixes are often used in some lists, and the > > >

Re: $reply_prefix

2022-01-14 Thread Derek Martin
On Fri, Jan 14, 2022 at 11:05:14AM +0300, Jean Louis wrote: >The "Subject:" field is the most common and contains a short >string identifying the topic of the message. When used in a >reply, the field body MAY start with the string "Re: " (an >abbreviation of the Latin "in re",

Re: $reply_prefix

2022-01-14 Thread Derek Martin
On Fri, Jan 14, 2022 at 09:10:19AM +0200, Tapani Tarvainen wrote: > On Thu, Jan 13, 2022 at 08:20:55PM -0800, Kevin J. McCarthy (ke...@8t8.us) > wrote: > > > I've been told other prefixes are often used in some lists, and the > > practice is getting more common. > > Other prefixes have also

Re: $reply_prefix

2022-01-14 Thread Derek Martin
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