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:01:08 +0800 [thread overview]
Message-ID: <87ppa1rkp7.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87a915c5an.fsf@building.gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Rasmus <rasmus@gmx.us> writes:
>
>>> Is that a bug or is it supposed to be that way?
>>
>> A bug, I hope!
>
> It was just me putting a non-existent viewer into the ~/.mailcap file,
> so it was filtered out again later. So that bit works.
>
> So the issue is really whether we should keep preferring Lisp-based
> (internal) viewers over external ones, even though the user has
> specified this in ~/.mailcap (or otherwise).
>
> That way of sorting seems to have been in place since 1998. But is it a
> good idea?
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'!
next prev parent reply other threads:[~2015-01-27 3:01 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 [this message]
2015-01-27 3:01 ` Lars Ingebrigtsen
2015-01-27 3:59 ` Eric Abrahamsen
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=87ppa1rkp7.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).