unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Blake Sweeney <blakes.85@gmail.com>
To: Patrick Totzke <patricktotzke@googlemail.com>,
	David Bremner <david@tethera.net>,
	Brian May <brian@microcomaustralia.com.au>,
	notmuch <notmuch@notmuchmail.org>
Subject: Re: emacs email appears empty
Date: Thu, 29 Sep 2011 08:49:39 -0400	[thread overview]
Message-ID: <4e846963.07bb650a.5fae.5d83@mx.google.com> (raw)
In-Reply-To: <4e845d44.89cde30a.5fa9.724c@mx.google.com>

On Thu, 29 Sep 2011 12:57:37 +0100, Patrick Totzke <patricktotzke@googlemail.com> wrote:
Non-text part: multipart/mixed
> 
> Quoting David Bremner (2011-09-29 12:05:37)
> >On Thu, 29 Sep 2011 11:21:21 +1000, Brian May <brian@microcomaustralia.com.au> wrote:
> >> Hello,
> >> 
> >> Have seen several cases now where the message appears blank in the
> >> emacs interface. With nothing but the headers.
> >> 
> >> Pushing Shift+V shows the entire raw message. Nothing special, just a
> >> plain text email without any attachments.
> >
> >Any chance you could share such a message with us?
> >
> >d
> 
> I have seen something like this using alot but thought i'd be an error in my code
> (did not test with emacs). It occurs with mails send as google sholar alerts.
> /p

I've seen something like this happen in the vim client as well. I've had it
occur with very few messages sent from an iPhone though. 

  reply	other threads:[~2011-09-29 12:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-29  1:21 emacs email appears empty Brian May
2011-09-29  1:22 ` Brian May
2011-09-29 11:05 ` David Bremner
2011-09-29 11:57   ` Patrick Totzke
2011-09-29 12:49     ` Blake Sweeney [this message]
2011-10-10 23:02   ` Brian May
2011-10-10 23:14     ` David Bremner
2011-10-01  0:31 ` 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=4e846963.07bb650a.5fae.5d83@mx.google.com \
    --to=blakes.85@gmail.com \
    --cc=brian@microcomaustralia.com.au \
    --cc=david@tethera.net \
    --cc=notmuch@notmuchmail.org \
    --cc=patricktotzke@googlemail.com \
    /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).