Gnus development mailing list
 help / color / mirror / Atom feed
From: David Abrahams <dave@boost-consulting.com>
Subject: Re: NTEmacs, smptpmail-queue-mail, and line-endings
Date: Sat, 09 Nov 2002 23:52:35 -0500	[thread overview]
Message-ID: <u3cqayqjw.fsf@boost-consulting.com> (raw)
In-Reply-To: <ud6pe2krd.fsf@boost-consulting.com>

David Abrahams <dave@boost-consulting.com> writes:

> 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?

Apparently I didn't get it right:

	-----Original Message----- 
	From: dave@boost-consulting.com [mailto:dave@boost-consulting.com] 
	Sent: Sat 11/9/2002 8:30 PM 
	To: <hidden>
	Cc: 
	Subject: 
	
	

	Subject: Testing
	
	From: David Abrahams <dave@boost-consulting.com>
	
	Date: Sat, 09 Nov 2002 21:39:20 -0500
	
	Message-ID: <uu1iq2lnr.fsf@boost-consulting.com>
	
	Lines: 14
	
	User-Agent: Gnus/5.090007 (Oort Gnus v0.07) Emacs/21.2
	
	 (i386-msvc-nt5.1.2600)
	
	MIME-Version: 1.0
	
	Content-Type: text/plain; charset=us-ascii
	
	Return-Path: dave@boost-consulting.com
	X-OriginalArrivalTime: 10 Nov 2002 04:30:52.0219 (UTC) FILETIME=[F3C410B0:01C28871]
	
	
	
	
	
	Hi Jason,
	
	
	
	Sorry to pester you... but how's the line spacing here?
	
	1
	
	2
	
	3
	
	4
	
	5
	
	
	
	--
	
	                       David Abrahams
	
	   dave@boost-consulting.com * http://www.boost-consulting.com
	
	Boost support, enhancements, training, and commercial distribution

-- 
                       David Abrahams
   dave@boost-consulting.com * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution



  reply	other threads:[~2002-11-10  4:52 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
2002-11-10  4:52     ` David Abrahams [this message]
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=u3cqayqjw.fsf@boost-consulting.com \
    --to=dave@boost-consulting.com \
    /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).