unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Make Message more RFC compliant
Date: Sat, 14 Apr 2018 09:36:45 +0300	[thread overview]
Message-ID: <83tvse47lu.fsf@gnu.org> (raw)
In-Reply-To: <87po32yeyy.fsf@mouse.gnus.org> (message from Lars Ingebrigtsen on Fri, 13 Apr 2018 23:27:17 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Fri, 13 Apr 2018 23:27:17 +0200
> 
> >>    Note: Some legacy implementations used the simple form where the
> >>    addr-spec appears without the angle brackets, but included the name
> >>    of the recipient in parentheses as a comment following the addr-spec.
> >>    Since the meaning of the information in a comment is unspecified,
> >>    implementations SHOULD use the full name-addr form of the mailbox,
> >>    instead of the legacy form, to specify the display name associated
> >>    with a mailbox.
> 
> So:
> 
> The RFC says SHOULD, so Message shouldn't have an easy way to generate
> >From headers that deviate from the `angles' style.
> 
> So I propose to remove the code that reacts to `message-from-style'
> (i.e., always generate `angles' From headers), and mark
> `message-from-style' as obsolete and note in the doc string that it's no
> longer used.
> 
> Any objections?

I don't understand why we need to remove the support code.  Making the
variable obsolete is OK, but if there's someone out there whose bad
habits die hard, or who needs to communicate with some weirdo mail
software that requires this obsolete format, why not let them do it?

Or am I missing something?



  reply	other threads:[~2018-04-14  6:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-13 21:27 Make Message more RFC compliant Lars Ingebrigtsen
2018-04-14  6:36 ` Eli Zaretskii [this message]
2018-04-14 13:04   ` Lars Ingebrigtsen
2018-04-14 13:27     ` Eli Zaretskii
2018-04-14 13:52       ` Lars Ingebrigtsen

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=83tvse47lu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).