From: David Edmondson <dme@dme.org>
To: Jani Nikula <jani@nikula.org>, notmuch@notmuchmail.org
Subject: Re: [PATCH 2/2] emacs: regard text/calendar as text/x-vcalendar
Date: Wed, 08 Feb 2012 17:06:45 +0000 [thread overview]
Message-ID: <cunty312r16.fsf@hotblack-desiato.hh.sledj.net> (raw)
In-Reply-To: <19a567d3e0c466ec6d73ba2039cf5a0d6c8bc3f5.1328719309.git.jani@nikula.org>
[-- Attachment #1: Type: text/plain, Size: 1606 bytes --]
On Wed, 8 Feb 2012 16:55:16 +0000, Jani Nikula <jani@nikula.org> wrote:
> Treat text/calendar as text/x-vcalendar. At least the following
> produce text/calendar that parse as text/x-vcalendar:
>
> PRODID:-//Google Inc//Google Calendar 70.9054//EN
> PRODID:Microsoft Exchange Server 2010
>
> Code by David Edmondson <dme@dme.org>
>
> ---
>
> I wish I had some references here, other than my own maildirs. Almost
> all of the calendar invites I have are text/calendar, and all of them
> parse just fine as text/x-vcalendar.
> ---
> emacs/notmuch-show.el | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/emacs/notmuch-show.el b/emacs/notmuch-show.el
> index 1340380..f6588b3 100644
> --- a/emacs/notmuch-show.el
> +++ b/emacs/notmuch-show.el
> @@ -720,6 +720,9 @@ current buffer, if possible."
> result)))
> t)
>
> +(defun notmuch-show-insert-part-text/calendar (msg part content-type nth depth declared-type)
> + (notmuch-show-insert-part-text/x-vcalendar msg part content-type nth depth declared-type))
> +
> (defun notmuch-show-insert-part-application/octet-stream (msg part content-type nth depth declared-type)
It seems that "text/calendar" is officially sanctioned and
"text/x-vcalendar" is old and being phased out, so these should really
be the other way around (i.e. text/calendar is the 'real' function that
is called by the text/x-vcalendar variant).
> ;; If we can deduce a MIME type from the filename of the attachment,
> ;; do so and pass it on to the handler for that type.
> --
> 1.7.1
>
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2012-02-08 17:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 16:55 [PATCH 0/2] multipart/alternative display and text/calendar Jani Nikula
2012-02-08 16:55 ` [PATCH 1/2] emacs: support defining a list of alternative parts to show Jani Nikula
2012-02-08 17:05 ` David Edmondson
2012-02-08 16:55 ` [PATCH 2/2] emacs: regard text/calendar as text/x-vcalendar Jani Nikula
2012-02-08 17:06 ` David Edmondson [this message]
2012-02-09 14:46 ` [PATCH v2 1/2] emacs: support defining a list of alternative parts to show Jani Nikula
2012-02-09 14:46 ` [PATCH v2 2/2] emacs: support text/calendar mime type Jani Nikula
2012-02-10 10:06 ` David Edmondson
2012-02-15 15:35 ` Adam Wolfe Gordon
2012-02-21 7:52 ` Jani Nikula
2012-02-25 13:55 ` David Bremner
2012-02-10 10:05 ` [PATCH v2 1/2] emacs: support defining a list of alternative parts to show David Edmondson
2012-02-10 10:17 ` Jani Nikula
2012-02-12 12:09 ` Jani Nikula
2012-02-12 14:37 ` Tomi Ollila
2012-02-21 7:50 ` Jani Nikula
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=cunty312r16.fsf@hotblack-desiato.hh.sledj.net \
--to=dme@dme.org \
--cc=jani@nikula.org \
--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).