unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Mark Walters <markwalters1009@gmail.com>
To: Adam Wolfe Gordon <awg+notmuch@xvx.ca>, notmuch@notmuchmail.org
Subject: Reply code with TEXT/PLAIN
Date: Sat, 24 Mar 2012 21:49:36 +0000	[thread overview]
Message-ID: <87d3814qkv.fsf@qmul.ac.uk> (raw)



I am not certain if this is a bug or a request to work around broken
mailers. I tried replying to a message today (with recent git) and got
an empty message. I looked at the json output for reply and it contains
the message but the content type is TEXT/PLAIN rather than
text/plain.

This seems to mean it doesn't match in notmuch-match-content-type
(notmuch-lib.el) called from notmuch-mua-get-quotable-parts (in
notmuch-mua.el); and so does not get included.

Making the match case-insensitive `fixed' the problem.

I don't know whether content-types are allowed  to be upper-case but I
seem to have several mails where they are. I am also not sure whether
the correct fix is in the emacs code, or in the cli reply format
(i.e. perhaps the reply format should lower-case the content-type).

Best wishes

Mark

PS Sorry Adam for the duplicate: I sent from a wrong address (my fault
this time)!

             reply	other threads:[~2012-03-24 21:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-24 21:49 Mark Walters [this message]
2012-03-25  0:19 ` Reply code with TEXT/PLAIN 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   ` Reply code with TEXT/PLAIN Jameson Graef Rollins
2012-03-26 15:24     ` 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=87d3814qkv.fsf@qmul.ac.uk \
    --to=markwalters1009@gmail.com \
    --cc=awg+notmuch@xvx.ca \
    --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).