Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <217E3C0C100E144B93AF131E71C6D62A031E7F72@edc-exchange.everdreamcorp.com>
From: David Byron <DByron AT everdreamcorp DOT com>
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: RE: Crontab on Win9X works
Date: Tue, 15 Apr 2003 11:01:29 -0700
MIME-Version: 1.0
Content-Type: text/plain

Igor Pechtchanski wrote:

> According to RFC 2822, a newline followed by whitespace is 
> going to be "unfolded" (so the newline is not "semantically 
> visible" in the header field).  The RFC also allows unfolding 
> lines consisting entirely of whitespace (but not blank lines!).
> 
> It seems to me that cron does not accomodate environment 
> values with whitespace in them at all.  A solution would be 
> to have cron insert a " " (space) after every newline in the
> variable value, which will render newlines harmless.  Does this
> make sense?

Yes.  It does alter the values of the environment variables with CRLF in
them, but that seems a lot better than what's happening now.  I can't find
something in the RFC that will allow CRLF to be retained as part of a header
field body.

-DB

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/