From: Neil Crellin <neilc@wallaby.cc>
Subject: Re: Pterodactyl Gnus v0.91 is released
Date: 05 Jul 1999 07:54:33 -0700 [thread overview]
Message-ID: <vb6btdruoye.fsf@webtile.wallaby.cc> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "05 Jul 1999 11:32:51 +0200"
Kai.Grossjohann@CS.Uni-Dortmund.DE writes:
> Neil Crellin <neilc@wallaby.cc> writes:
>
> > Using string= in place of string-match here is doing the totally wrong
> > thing with regard to wildcard matches in the mailcap parsing. I suggest
> > reverting that particular sub-patch. I'm not seeing what exactly that
> > patch was needed for, so I don't know if this breaks anything else,
> > but it does fix wildcard mailcap matches.
>
> Somebody had a string "c++" in there, and using string-match didn't
> find it. (I forgot the exact details.)
>
> Can we make it grok "c++" and wildcards?
>
> What is wildcard matching in mailcap parsing supposed to do?
A fairly common artifice in mailcaps are things like the following:
audio/*; /usr/bin/play %s
image/*; xv %s
video/*; xanim %s
In the example I was trying, mailcap-possible-viewers on an image/gif
was found to match no viewer with the above mailcap definition when
string= replaced string-match. With string-match, the viewer was
determined to be "xv %s".
--
Neil Crellin <neilc@wallaby.cc>
next prev parent reply other threads:[~1999-07-05 14:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-04 6:32 Lars Magne Ingebrigtsen
1999-07-04 7:55 ` Michael Klingbeil
1999-07-05 1:10 ` Neil Crellin
1999-07-05 2:11 ` Neil Crellin
1999-07-05 2:25 ` Neil Crellin
1999-07-05 3:36 ` Lars Magne Ingebrigtsen
1999-07-05 9:32 ` Kai.Grossjohann
1999-07-05 14:54 ` Neil Crellin [this message]
1999-07-05 15:00 ` Hrvoje Niksic
1999-07-05 10:25 ` William M. Perry
1999-07-06 4:09 ` Lars Magne Ingebrigtsen
1999-07-05 15:43 ` Neil Crellin
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=vb6btdruoye.fsf@webtile.wallaby.cc \
--to=neilc@wallaby.cc \
/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).