From: wmperry@aventail.com (William M. Perry)
Cc: Gnus Mailing List <ding@gnus.org>
Subject: Re: %{...} in mailcap (was: bugs in mailcap (patch: 93-zsh3))
Date: 09 Jul 1999 11:47:08 -0500 [thread overview]
Message-ID: <86emihwz1v.fsf@kramer.bp.aventail.com> (raw)
In-Reply-To: Shenghuo ZHU's message of "09 Jul 1999 12:20:14 -0400"
Shenghuo ZHU <zsh@cs.rochester.edu> writes:
> >>>>> "LMI" == Lars Magne Ingebrigtsen <bugs@gnus.org> writes:
>
> >> Here the patch. By the way, I guess mm-display-external do not handle
> >> %-sequences like %{name}, %{patchnumber}.
>
> LMI> No, it doesn't -- I didn't even know that one could do that. Is the
> LMI> mailcap format specified anywhere?
>
> The following is cited from mailcap manual of RedHat 6.0 (by Nathaniel
> S. Borenstein).
The original mm.el code handles this type of thing in
'mm-unescape-mime-test' but I don't think it did it when actually passing
things to the viewers.
(cond
((null save-chr) nil)
((= save-chr ?t)
(delete-region save-pos (progn (forward-char 1) (point)))
(insert (or (cdr (assoc "type" type-info)) "\"\"")))
((= save-chr ?M)
(delete-region save-pos (progn (forward-char 1) (point)))
(insert "\"\""))
((= save-chr ?n)
(delete-region save-pos (progn (forward-char 1) (point)))
(insert "\"\""))
((= save-chr ?F)
(delete-region save-pos (progn (forward-char 1) (point)))
(insert "\"\""))
>>>> ((= save-chr ?{)
>>>> (forward-char 1)
>>>> (skip-chars-forward "^}")
>>>> (downcase-region (+ 2 save-pos) (point))
>>>> (setq subst (buffer-substring (+ 2 save-pos) (point)))
>>>> (delete-region save-pos (1+ (point)))
>>>> (insert (or (cdr (assoc subst type-info)) "\"\"")))
(t nil))
-bp
next prev parent reply other threads:[~1999-07-09 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2nhfnfwrsz.fsf@tiger.jia.vnet>
[not found] ` <m3u2rdq0zn.fsf@quimbies.gnus.org>
1999-07-09 16:20 ` Shenghuo ZHU
1999-07-09 16:47 ` William M. Perry [this message]
1999-07-09 21:31 ` 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=86emihwz1v.fsf@kramer.bp.aventail.com \
--to=wmperry@aventail.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).