Gnus development mailing list
 help / color / mirror / Atom feed
From: John Williams <john.williams@otago.ac.nz>
To: ding@gnus.org
Subject: Re: MIME parts not saved
Date: Mon, 05 Aug 2013 14:35:11 +1100	[thread overview]
Message-ID: <87txj4kdxs.fsf@otago.ac.nz> (raw)
In-Reply-To: <b4m8v0hot3a.fsf@jpl.org>

Katsumi Yamaoka <yamaoka@jpl.org> writes:

> The solution I took then was to remove xdg-open from the mailcap
> database, as described in the article.  You may want to add the
> entries to the database[1] for the pairs of the content-types and
> the viewers if Fedora doesn't provide them in the system mailcap
> database.  To know what entries there are, do
> `M-x load-library RET mailcap RET' and
> `C-h v mailcap-mime-data RET'.
>
> [1] An easy way is to have the ~/.mailcap file with the entries
>     like the following:
>
> application/pdf; /usr/bin/acroread %s
> application/msword; /usr/bin/ooffice %s
>
>     Note that whenever you edited the file you have to do
>     `M-x mailcap-parse-mailcaps RET', or restart Emacs and Gnus.
That works great, thank you so much!  But if this is a common problem,
perhaps it should be noted in the Gnus manual, in the section about
dealing with MIME parts?

>> So then I try to save the part locally, am prompted for a location and
>> save the file.  Great!  The file is created. Except that when I go to
>> open it, I find that it is empty, i.e. 0 bytes.
>
> I don't know.  Is it always empty for any attachment?
I forgot that I had set nnimap to only download non-MIME parts from the
server. As soon as Lars asked if there was anything in the attachment, I
remembered. I'm sorry to have bothered you and Lars with this silly
question.

Thanks for your help,

John




  reply	other threads:[~2013-08-05  3:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02  6:17 John Williams
2013-08-03 11:25 ` Lars Magne Ingebrigtsen
2013-08-05  3:31   ` John Williams
2013-08-05  0:54 ` Katsumi Yamaoka
2013-08-05  3:35   ` John Williams [this message]
2013-08-05 11:25     ` Katsumi Yamaoka
2013-08-05 15:16       ` Katsumi Yamaoka
2013-08-06 13:52         ` Katsumi Yamaoka
2013-08-07 14:22           ` Dan Christensen
2013-08-08  0:43             ` Katsumi Yamaoka
2013-08-09  8:06               ` Katsumi Yamaoka
2013-08-09 23:20                 ` Dan Christensen
2013-08-12  2:38                   ` Katsumi Yamaoka
2013-08-12  5:59                     ` Katsumi Yamaoka
2013-08-12 14:09                     ` Dan Christensen
2013-08-12 17:18                       ` Lars Magne Ingebrigtsen
2013-08-13  2:29                         ` Dan Christensen
2013-08-13  4:02                           ` Katsumi Yamaoka
2013-08-13  5:22                             ` Katsumi Yamaoka
2013-08-13 10:43                             ` Adam Sjøgren
2013-08-13 20:47                               ` Dan Christensen
2013-08-13 23:50                                 ` Katsumi Yamaoka
2013-08-14  1:41                                   ` Dan Christensen
2013-08-14  8:52                                     ` Adam Sjøgren
2013-08-14  8:58                                   ` Adam Sjøgren

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=87txj4kdxs.fsf@otago.ac.nz \
    --to=john.williams@otago.ac.nz \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).