unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: irek <mail@gumen.pl>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Fixed order of headers in Rmail messages
Date: Thu, 10 Feb 2022 11:26:43 +0300	[thread overview]
Message-ID: <YgTMQxDn1ieTi5FH@protected.localdomain> (raw)
In-Reply-To: <871r0bxi17.fsf@mother.org>

* irek <mail@gumen.pl> [2022-02-10 11:24]:
> Jean Louis <bugs@gnu.support> writes:
> > RFC 5322: Internet Message Format
> > https://www.rfc-editor.org/rfc/rfc5322.html#section-3.6
> >
> > Quote:
> >
> > ,----
> > | It is important to note that the header fields are not guaranteed to
> > | be in a particular order.
> > `----
> 
> Thanks for source.  I don't expect from the messages to arrived with
> headers in particular order.  I just want to display them sorted in
> Rmail buffer.
> 
> I will try to look at rmail-copy-headers function suggested by Eli and
> keep headers in original messages unchanged.

You are right. I can see that other mail user software also displays
headers in particular order, like in Mutt, I see 1) Date, 2) From, 3)
To, 4) Cc, 5) Bcc, 6) Subject always in the same order.

Consistent order of those most important header fields is user
interface accessibility issue. 

IMHO, RMail should display basic headers in consistent order.

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/



  reply	other threads:[~2022-02-10  8:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09 21:43 Fixed order of headers in Rmail messages irek
2022-02-10  6:05 ` Tassilo Horn
2022-02-10  7:21   ` irek
2022-02-10  7:44   ` Eli Zaretskii
2022-02-10  8:37     ` Tassilo Horn
2022-02-10 12:03       ` Eli Zaretskii
2022-02-10  6:06 ` Eli Zaretskii
2022-02-10  7:17   ` irek
2022-02-10  7:54 ` Jean Louis
2022-02-10  8:06   ` irek
2022-02-10  8:26     ` Jean Louis [this message]
2022-02-12 12:27 ` irek
2022-02-12 18:37   ` Jean Louis
2022-02-12 23:10     ` irek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YgTMQxDn1ieTi5FH@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=help-gnu-emacs@gnu.org \
    --cc=mail@gumen.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).