From: Steinar Bang <sb@dod.no>
Subject: Re: K v uses eeyes, even though mailcap uses xzgv (Was: OORT.jpg)
Date: Sun, 27 Jan 2002 21:36:20 +0100 [thread overview]
Message-ID: <87g04rzg3f.fsf@bang.priv.no> (raw)
In-Reply-To: <vaf8zajbrc2.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
>>>>> grossjoh@lothlorien.cs.uni-dortmund.de (Kai Großjohann):
> IMVHO, the user putting "image/*; xv %s" in ~/.mailcap clearly
> indicates that they want to use xv for all images.
> So image/* in the personal file should override the image/foo
> entries in the system-wide file.
That's the behaviour I expected.
> But of course, the image/foo entry in ~/.mailcap should overrade the
> image/* entry there, and similar for the system-wide file.
Agreed.
next prev parent reply other threads:[~2002-01-27 20:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 16:50 OORT.jpg luis fernandes
2002-01-15 17:09 ` OORT.jpg Per Abrahamsen
2002-01-16 0:12 ` OORT.jpg Katsumi Yamaoka
2002-01-16 4:37 ` OORT.jpg Russ Allbery
2002-01-16 7:15 ` OORT.jpg Katsumi Yamaoka
2002-01-16 2:40 ` OORT.jpg Lars Magne Ingebrigtsen
2002-01-16 13:01 ` OORT.jpg luis fernandes
2002-01-16 13:23 ` OORT.jpg Lars Magne Ingebrigtsen
2002-01-26 22:07 ` K v uses eeyes, even though mailcap uses xzgv (Was: OORT.jpg) Steinar Bang
2002-01-26 22:14 ` Lars Magne Ingebrigtsen
2002-01-27 9:37 ` Steinar Bang
2002-01-26 23:53 ` Daniel Pittman
2002-01-27 12:01 ` Kai Großjohann
2002-01-27 16:30 ` Steinar Bang
2002-01-27 17:29 ` Kai Großjohann
2002-01-27 18:00 ` Lars Magne Ingebrigtsen
2002-01-27 18:06 ` K v uses eeyes, even though mailcap uses xzgv Norbert Koch
2002-01-27 18:07 ` K v uses eeyes, even though mailcap uses xzgv (Was: OORT.jpg) Kai Großjohann
2002-01-27 20:36 ` Steinar Bang [this message]
2003-01-02 3:24 ` K v uses eeyes, even though mailcap uses xzgv Lars Magne Ingebrigtsen
2003-01-02 17:10 ` Kai Großjohann
2003-01-02 19:54 ` Lars Magne 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=87g04rzg3f.fsf@bang.priv.no \
--to=sb@dod.no \
/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).