[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters
From: |
Lyndon Nerenberg |
Subject: |
Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters |
Date: |
Thu, 6 Oct 2016 20:14:17 -0700 |
> On Oct 6, 2016, at 8:11 PM, David Levine <address@hidden> wrote:
>
> But I wouldn't consider the likely result with filename=/foo/bar/README
> to be safest.
Why not? If there is no "README" file, create it. If there is, prompt for a
replacement if stdin is a tty, else synthesize a unique replacement name and be
done with it.
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, (continued)
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, Ralph Corderoy, 2016/10/07
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, Earl Hood, 2016/10/05
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, David Levine, 2016/10/06
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, Lyndon Nerenberg, 2016/10/06
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, Lyndon Nerenberg, 2016/10/06
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, David Levine, 2016/10/06
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters,
Lyndon Nerenberg <=
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, David Levine, 2016/10/07
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, Ralph Corderoy, 2016/10/10
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, Ken Hornstein, 2016/10/10
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, Ken Hornstein, 2016/10/03
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, Paul Vixie, 2016/10/03
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, Paul Vixie, 2016/10/03