From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Adam Wolfe Gordon <awg+notmuch@xvx.ca>,
Mark Walters <markwalters1009@gmail.com>
Cc: notmuch@notmuchmail.org
Subject: Re: Reply code with TEXT/PLAIN
Date: Mon, 26 Mar 2012 08:21:21 -0700 [thread overview]
Message-ID: <8762drl766.fsf@servo.finestructure.net> (raw)
In-Reply-To: <CAMoJFUuGS_y4Sqtug5Ohdic3M43_fexWOt7cAw-ebuZ_SVUnjQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
On Sat, 24 Mar 2012 18:19:50 -0600, Adam Wolfe Gordon <awg+notmuch@xvx.ca> wrote:
> A bit of Googling indicates that MIME types should be case insensitive
> (i.e. TEXT/PLAIN should match text/plain). Given this, I think it
> makes sense to change the emacs function regardless of whether it
> makes sense for the CLI to output them in lower-case.
Does it make sense for the cli to canonicalize the content types to
always be lower case? Or should it continue to just pass the content
type exactly as it appears in the original message? Given that
consumers should parse it case insensitively, it maybe doesn't matter,
but it might also be nice for us to be consistent. Maybe it's just ok
as it is.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2012-03-26 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 21:49 Reply code with TEXT/PLAIN Mark Walters
2012-03-25 0:19 ` Adam Wolfe Gordon
2012-03-25 0:43 ` [PATCH] emacs: content-type comparison should be case insensitive Mark Walters
2012-03-26 15:21 ` Jameson Graef Rollins
2012-03-26 19:40 ` Tomi Ollila
2012-03-31 0:30 ` David Bremner
2012-03-26 15:21 ` Jameson Graef Rollins [this message]
2012-03-26 15:24 ` Reply code with TEXT/PLAIN Daniel Kahn Gillmor
2012-03-26 15:39 ` Jameson Graef Rollins
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8762drl766.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=awg+notmuch@xvx.ca \
--cc=markwalters1009@gmail.com \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).