From: Christoph Conrad <C.Conrad@cli.de>
Subject: Re: attachment names
Date: 03 Nov 2000 14:19:03 +0100 [thread overview]
Message-ID: <usnp9i46w.fsf@cli.de> (raw)
In-Reply-To: <ilupukd1bsx.fsf@barbar.josefsson.org>
>>>>> "Simon" == Simon Josefsson <sj@extundo.com> writes:
Simon> The following won't require modifying gnus, which probably is
Simon> more future-safe.
Good, it works.
But it seems to interact with the extension described in:
gnus.ding
Message-ID: <2nvgu5y4cm.fsf@tiger.jia.vnet>
!* [ 31: ShengHuo ZHU ] Re: Suggestion for saving attachments
Try to externalize an attachement like this, and then redisplay the
message/news. In my gnus the redisplayed message has a garbage looking
attachment.
Simon> Do you all think Gnus should handle this by default, even
Simon> though it's wrong? It would cause problems (only) if someone
Simon> actually intended the filename to be a valid QP encoded word.
Simon> That isn't very likely IMHO.
Maybe you could make it optional (switchable).
Mit freundlichen Grüßen / Best regards
i. A.
Christoph Conrad
--
CLI-GmbH, Matthiashofstr. 28-30, D-52064 Aachen
Fon: +49 241 47051-0 Fax: +49 241 47051-89 Web: http://www.cli.de
(defvar my-computer '((OS . "GNU Emacs") (system-type . gnu/linux))
"Programming environment.")
next prev parent reply other threads:[~2000-11-03 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-02 13:17 Vladimir Volovich
2000-11-02 13:44 ` Simon Josefsson
2000-11-03 11:50 ` Christoph Conrad
[not found] ` <ud7gd9sw1.fsf@cli.de>
2000-11-03 12:26 ` Simon Josefsson
2000-11-03 13:13 ` Kai Großjohann
2000-11-03 14:40 ` Per Abrahamsen
2000-11-03 13:19 ` Christoph Conrad [this message]
2000-11-03 13:37 ` Christoph Conrad
2000-11-03 14:39 ` Per Abrahamsen
2000-11-03 15:31 ` Simon Josefsson
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=usnp9i46w.fsf@cli.de \
--to=c.conrad@cli.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).