From: Jack Vinson <jvinson@chevax.ecs.umass.edu>
Subject: MML plain attachment from NTemacs
Date: 11 Jun 1999 14:31:28 -0500 [thread overview]
Message-ID: <wkpv321qlr.fsf@chevax.ecs.umass.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 396 bytes --]
I just discovered that MML is not using the correct coding system when it
attaches a file from NTemacs. The attached file looks just fine when I
edit it, but when I send there are two Ctrl-M characters added to the end
of each line. Not only does this suggest a bad coding-system, but it
sounds like the coding system is wrong a couple times.
Has anyone seen this or fixed it?
An attachment:
[-- Attachment #2: Testing Attachment --]
[-- Type: text/plain, Size: 46 bytes --]
This is a plain text file.
It is also a test.
[-- Attachment #3: Type: text/plain, Size: 178 bytes --]
--
Jack Vinson <jvinson@chevax.ecs.umass.edu> http://www.cis.upenn.edu/~vinson/
Zippy: I'm meditating on the FORMALDEHYDE and the ASBESTOS leaking into my
PERSONAL SPACE!!
next reply other threads:[~1999-06-11 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-11 19:31 Jack Vinson [this message]
1999-06-11 21:26 ` Kai.Grossjohann
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=wkpv321qlr.fsf@chevax.ecs.umass.edu \
--to=jvinson@chevax.ecs.umass.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).