From: "Arne Jørgensen" <arne@daimi.au.dk>
Subject: Re: multiple mailcap entries
Date: Mon, 14 Apr 2003 08:38:34 +0200 [thread overview]
Message-ID: <yiiadettwgl.fsf@horse05.daimi.au.dk> (raw)
In-Reply-To: <m3fzooesro.fsf@defun.localdomain>
Jesper Harder <harder@myrealbox.com> writes:
> I guess to fix the logic in mailcap.el to observe this order of priority
> if mailcap.el specifies an internal command:
>
> ~/.mailcap
> mailcap.el
> /etc/mailcap
> /usr/etc/mailcap
> /usr/local/etc/mailcap
>
> but this order if the entry in mailcap.el is an external command:
>
> ~/.mailcap
> /etc/mailcap
> /usr/etc/mailcap
> /usr/local/etc/mailcap
> mailcap.el
Why not invent a ~/.mailcap.el and put it at the beginning of the
search path?
That way it doesn't matter whether it is an internal or external
command. If the command is specified in ~/.mailcap.el it is the
command that is to run from emacs.
Kind reagrds,
--
stud. scient. Arne Jørgensen
Kollegium 5, 2. v. 222, Universitetsparken, DK-8000 Aarhus C, Denmark
phone: +45 89 42 72 22, mobile: +45 21 65 01 13
email: arne@daimi.au.dk, <http://www.daimi.au.dk/~arne/>
next prev parent reply other threads:[~2003-04-14 6:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 13:10 Klaus Zeitler
2003-04-09 14:52 ` Jesper Harder
[not found] ` <84k7e16o11.fsf@lucy.is.informatik.uni-duisburg.de>
[not found] ` <m3d6jseslm.fsf@defun.localdomain>
[not found] ` <84znmw7ov2.fsf@lucy.is.informatik.uni-duisburg.de>
2003-04-11 20:58 ` Jesper Harder
[not found] ` <q5gsmspnnmr.fsf@lucent.com>
[not found] ` <m3fzooesro.fsf@defun.localdomain>
[not found] ` <i7he9396e8.fsf@hilbert.math.albany.edu>
[not found] ` <m3adevu7il.fsf@defun.localdomain>
[not found] ` <84brzbvj0v.fsf@lucy.is.informatik.uni-duisburg.de>
2003-04-12 15:32 ` Adam Sjøgren
2003-04-12 16:21 ` Vasily Korytov
2003-04-12 16:27 ` Vasily Korytov
2003-04-14 6:38 ` Arne Jørgensen [this message]
[not found] ` <85istme3yw.fsf.Hubert.Canon@alussinan.org>
[not found] ` <m3r88a8i6c.fsf@defun.localdomain>
2003-04-11 10:53 ` Gnus and indentation Hubert Canon
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=yiiadettwgl.fsf@horse05.daimi.au.dk \
--to=arne@daimi.au.dk \
/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).