From: reader@newsguy.com
To: ding@gnus.org
Subject: Re: Designate viewing application for mime types
Date: Sat, 26 May 2007 07:42:43 -0400 [thread overview]
Message-ID: <87ejl3olos.fsf@newsguy.com> (raw)
In-Reply-To: <873b1jltuv.fsf@newsguy.com>
reader@newsguy.com writes:
> I tried to add a special viewer in .../lisp/mailcap.el around line
> 141 (at the asterisks below) after commenting out `gv -safer'.
> Then renamed mailcap.elc mailcap.elcX and restarted gnus forcing it to
> load source file mailcap.el with modification.
>
> Its probably in the wrong place or isn't used in this way... but at any
> rate it didn't change anything. Pressing RET on an *.pdf just goes
> immediately to save dialog where as it did try to use gv before the edit.
Sorry I misspoke. The edit actually was redone after the gnus restart
so I just M-x load-file 'd it.
I then thought perhaps that would not be enough and again restarted.
Then the custome viewer was invoked.
But still, editing source files to get a desired result is not a plan
since it would get erased on updates etc.
So to reiterate... I was unable to discover a way to use the suggested
commands: `mailcap-add (or maybe mailcap-add-mailcap-entry)'
but still would like to see some lines to add to gnus.el to
invoke custom viewers. Or possibly some simple OS related way.
mailcap.el doesn't mention *.jpg except in a long list off exensions,
pressing a *.jpg invokes an ImageMagick cmd (display) from somewhere.
(not /etc/mailcap) and I don't know where it comes from.
I'm running gentoo linux with kde desktop.
next prev parent reply other threads:[~2007-05-26 11:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 13:04 reader
2007-05-25 13:06 ` Leo
2007-05-25 13:14 ` reader
2007-05-25 13:17 ` Leo
2007-05-25 13:49 ` reader
2007-05-26 0:45 ` Kevin Ryde
2007-05-26 11:14 ` reader
2007-05-26 11:42 ` reader [this message]
2007-05-26 12:27 ` Reiner Steib
2007-05-26 20:47 ` reader
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=87ejl3olos.fsf@newsguy.com \
--to=reader@newsguy.com \
--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).