all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: rfc2047-decode-region
Date: Mon, 02 Jan 2012 22:18:12 +0900	[thread overview]
Message-ID: <87mxa61bvv.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <83mxa8stev.fsf@gnu.org>

Eli Zaretskii writes:

 > > It's all in RFC 5322.  Doesn't everybody know that by heart? ;-)
 > 
 > I didn't find a place that would explain how to compute 5322 from
 > 2047.

I didn't either; that's why you need to know the RFC by heart.  Seems
a reasonable requirement for participation in a project which chooses
its infrastructure based on email controllability! :-)

 > Thanks.  I needed it to decode a region of the "rmail view buffer",
 > where we display a single message, which includes all the displayed
 > headers, including From, To, CC, Subject, etc.  So from your
 > explanations I understand that the ADDRESS-MIME argument can stay nil
 > in that case, correct?

Yes, if I were you I'd set it to nil.  Setting it to t makes some
*extremely* rare addresses (eg <"an\ RFC\-legit\ address"@gnu.org>,
and that is *not* a joke, it's the kind of example that ADDRESS-MIME
is intended for) look nicer.  But it probably would do really
confusing things to program strings in unstructured fields (eg, Lisp
regexps in the Subject field), and I think those are much more likely
than mailboxes whose names contain special characters.




  reply	other threads:[~2012-01-02 13:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-31 10:11 rfc2047-decode-region Eli Zaretskii
2011-12-31 12:48 ` rfc2047-decode-region Stephen J. Turnbull
2011-12-31 14:32   ` rfc2047-decode-region Eli Zaretskii
2012-01-02 13:18     ` Stephen J. Turnbull [this message]
2012-01-02 17:33       ` rfc2047-decode-region Eli Zaretskii

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

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

  git send-email \
    --in-reply-to=87mxa61bvv.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.