From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: [MAILCAP] filename quoting
Date: 27 Feb 2001 23:09:41 +0100 [thread overview]
Message-ID: <vafzof7pyl6.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <mux8zmsney1.fsf@uzeb.lrde.epita.fr> (Didier Verna's message of "27 Feb 2001 19:44:38 +0100")
On 27 Feb 2001, Didier Verna wrote:
> After some more thinking, the following solution might be the
> simplest one. If there's no objection, I'll apply it:
I'm not sure I understand the code. I guess it looks for '%s' in the
mailcap file and then does something special. Does it omit the call
to mm-quote-arg? Or does it replace '%s' with %s and then do
mm-quote-arg?
I think it might forget to look for "%s" in addition to '%s' -- some
people might have the double quotes rather than single quotes.
kai
--
Be indiscrete. Do it continuously.
next prev parent reply other threads:[~2001-02-27 22:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 18:23 Didier Verna
2001-02-27 18:44 ` Didier Verna
2001-02-27 22:09 ` Kai Großjohann [this message]
2001-02-28 8:18 ` Didier Verna
2001-02-28 15:41 ` Kai Großjohann
2001-02-28 16:10 ` Toby Speight
2001-02-28 20:06 ` Kai Großjohann
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=vafzof7pyl6.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).