From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: [MAILCAP] filename quoting
Date: 28 Feb 2001 16:41:46 +0100 [thread overview]
Message-ID: <vafy9uqu85h.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <muxpug3mda6.fsf@uzeb.lrde.epita.fr> (Didier Verna's message of "28 Feb 2001 09:18:09 +0100")
On 28 Feb 2001, Didier Verna wrote:
> What still bothers me in this solution is that we're somewhat doing
> the shell's job in understanding and processing its quoting
> syntax. That still remains affordable in those simple cases,
> however.
Yes. There needs to be an agreement between different programs on
what should be in ~/.mailcap. Maybe comp.mail.mime is the right place
to discuss that?
Failing any other possibility, we could either decide to do whatever
the metamail package does, or we could decide to do the Right Thing
(tm) -- having Gnus quote the file names.
Thoughts?
kai
--
Be indiscrete. Do it continuously.
next prev parent reply other threads:[~2001-02-28 15:41 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
2001-02-28 8:18 ` Didier Verna
2001-02-28 15:41 ` Kai Großjohann [this message]
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=vafy9uqu85h.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).