Gnus development mailing list
 help / color / mirror / Atom feed
From: david.goldberg6@verizon.net (Dave Goldberg)
To: ding@gnus.org
Subject: Re: Recent Emacs doesn't respect my mailcap
Date: Tue, 27 Jan 2015 20:54:54 -0500	[thread overview]
Message-ID: <841tmf7jpt.fsf@davestoy.home> (raw)
In-Reply-To: <87lhkoq081.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of	"Tue, 27 Jan 2015 13:08:46 +0800")

> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>
>>> 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.
>>
>> The `-externally' command should work different from the other command,
>> shouldn't it?  Otherwise, what's the point of having two of these
>> commands?
>
> Good point!
>

So I've been silently grumbling about this issue for a couple months, but I've just gotten used to calling ...-view-part-interactively (from the context menu) and running acrobat reader.  docview is really not an option at work (where most of my PDF dealings come from) since my company uses some of the more irritating PDF features like digital signatures.  Whether that's done via view-part or view-part-externally (assuming there's a strong desire to have view-part favor an internal function) doesn't bother me but it would be nice if view-part-externally did what I told it to do.

Thanks,
-- 
Dave Goldberg
david.goldberg6@verizon.net



  reply	other threads:[~2015-01-28  1:54 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
2015-01-27  4:47                     ` Lars Ingebrigtsen
2015-01-27  5:08                       ` Eric Abrahamsen
2015-01-28  1:54                         ` Dave Goldberg [this message]
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=841tmf7jpt.fsf@davestoy.home \
    --to=david.goldberg6@verizon.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).