From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Recent Emacs doesn't respect my mailcap
Date: Tue, 27 Jan 2015 11:59:24 +0800 [thread overview]
Message-ID: <87fvawri03.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87386xc4fh.fsf@building.gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> In my use case, I've already told Gnus to view the PDF externally by
>> using `gnus-article-view-part-externally'. Given that, and the fact that
>> I've specified an external viewer in ~/.mailcap, it seems a little
>> perverse that I'm still stuck seeing it in Doc View. If I wanted to do
>> that, I could have just called `gnus-article-view-part'!
>
> That does sound like a bug. Perhaps that command should filter out all
> Lisp functions from `mailcap-mime-data'?
Or put ~/.mailcap stuff at the front of the list, or maybe just don't
re-sort mailcap-mime-data. I don't think anything fancy needs to be done
-- it should be enough just to *not* mess with mailcap-mime-data. At
least users will have an easier time figuring out what's happening.
Dunno, really.
next prev parent reply other threads:[~2015-01-27 3:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.18666.1422291069.1147.help-gnu-emacs@gnu.org>
[not found] ` <87386xf5gx.fsf@building.gnus.org>
[not found] ` <mailman.18710.1422322318.1147.help-gnu-emacs@gnu.org>
[not found] ` <87386xdmzp.fsf@building.gnus.org>
[not found] ` <mailman.18712.1422322837.1147.help-gnu-emacs@gnu.org>
2015-01-27 1:58 ` Lars Magne Ingebrigtsen
2015-01-27 2:11 ` Rasmus
2015-01-27 2:42 ` Lars Ingebrigtsen
2015-01-27 3:01 ` Eric Abrahamsen
2015-01-27 3:01 ` Lars Ingebrigtsen
2015-01-27 3:59 ` Eric Abrahamsen [this message]
2015-01-27 4:47 ` Lars Ingebrigtsen
2015-01-27 5:08 ` Eric Abrahamsen
2015-01-28 1:54 ` Dave Goldberg
2015-01-29 2:21 ` Lars Ingebrigtsen
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=87fvawri03.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).