From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Trouble with attachments
Date: Thu, 21 Mar 2002 14:41:28 -0500 [thread overview]
Message-ID: <2n7ko54sk7.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <dnd6xxuang.fsf@magla.zg.iskon.hr> (Zlatko Calusic's message of "Thu, 21 Mar 2002 17:51:31 +0100")
Zlatko Calusic <zlatko.calusic@iskon.hr> writes:
> Using attachments in XEmacs/Gnus is simple. You just middle click on
> your attachment and Gnus fires appropriate helper applications. Yes.
>
> But, that doesn't work if attachment filename has spaces inside it.
>
> I don't know if it is XEmacs' or Gnus' bug, but it is definitely a
> long standing (and annoying) one. My apologies if I'm barking up the
> wrong tree.
It is related to mailcap files in debian. The problem is who should
quotes file names, MUA or mailcap. The RFC1524 doesn't mention it.
Gnus quotes file names because most mailcap files don't. Mailcap files
in debian quote file names with quotation marks, but, IMHO, it doesn't
entirely solve the problem because file names may contain quotation
marks too.
ShengHuo
prev parent reply other threads:[~2002-03-21 19:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 16:51 Zlatko Calusic
2002-03-21 19:41 ` ShengHuo ZHU [this message]
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=2n7ko54sk7.fsf@zsh.cs.rochester.edu \
--to=zsh@cs.rochester.edu \
/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).