From: David Abrahams <dave@boost-consulting.com>
Cc: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: NTEmacs, smptpmail-queue-mail, and line-endings
Date: Sat, 09 Nov 2002 21:58:46 -0500 [thread overview]
Message-ID: <ud6pe2krd.fsf@boost-consulting.com> (raw)
In-Reply-To: <84el9wb8dl.fsf@crybaby.uni-duisburg.de>
kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
> David Abrahams <dave@boost-consulting.com> writes:
>
>> And some Linux users have problems, too (see bottom of this
>> message). The email looks fine to me on its way out; my best guess is
>> that the DOS '\r\n' line ending convention is messing things up. The
>> files stored in ~/Mail/queued-mail, waiting to go out. do indeed have
>> DOS line-endings.
>
> Maybe you can tell Emacs to use Unix line endings in that directory.
> See the variable file-coding-system-alist. Does this help?
I don't know. It might. I added
(setq file-coding-system-alist
(cons
(cons
(concat (expand-file-name "~/Mail/queued-mail/") "[^.]+\\'")
'(emacs-mule-dos . undecided-unix))
file-coding-system-alist))
to my .gnus file. However, I'm sufficiently clueless about coding
systems that it's hard to tell what the right thing to do is. For
example, when is a file encoded? When is it decoded?
--
David Abrahams
dave@boost-consulting.com * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution
next prev parent reply other threads:[~2002-11-10 2:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 14:56 David Abrahams
2002-11-06 19:17 ` David Abrahams
2002-11-08 11:36 ` Kai Großjohann
2002-11-10 2:58 ` David Abrahams [this message]
2002-11-10 4:52 ` David Abrahams
2002-11-11 16:35 ` 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=ud6pe2krd.fsf@boost-consulting.com \
--to=dave@boost-consulting.com \
--cc=kai.grossjohann@uni-duisburg.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).