From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25167 invoked by alias); 2 Jul 2003 16:50:42 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 25155 invoked from network); 2 Jul 2003 16:50:41 -0000 Received: from unknown (HELO smtp2.fre.skanova.net) (195.67.227.95) by sources.redhat.com with SMTP; 2 Jul 2003 16:50:41 -0000 Received: from p450 (t3o73p108.telia.com [62.20.219.108]) by smtp2.fre.skanova.net (8.12.9/8.12.9) with SMTP id h62GoZNt012969 for ; Wed, 2 Jul 2003 18:50:40 +0200 (CEST) From: "Hannu E K Nevalainen (garbage mail)" To: Subject: RE: CRLF to LF Issue Date: Wed, 02 Jul 2003 16:50:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal In-Reply-To: X-SW-Source: 2003-07/txt/msg00129.txt.bz2 FYI... :-} I've been in this situation since 1985 or so... (Amiga user since then. AmigaOS uses LF EOL. Also been using MS "OS'es" since before '85). "My way" has been: 1) Keep each OS clean of files not having the default line ending 2) Make sure to always CONVERT files _at the very moment_ they're transferred i.e. files in "cygwin" file tree should always have LF EOL. Move/Copy out of the 'file tree' and immediately convert accordingly. A simple "$ find -type f | xargs u2d" (or some such; not checked) should do the trick in one go. IMHO the mere possibility to switch between EOL-conventions on cygwin is a nuisance. It just generates problems[1] without any clear benefit for anything. /Hannu E K Nevalainen, Mariefred, Sweden -- [1] Problems: * User interaction i.e. The user inadverently does something that causes EOL's to be otherwise than expected. * Initial implementation The source has to be converted (at least in some cases) to handle the possible switch. * Updating the source Upstream changes might cause a rewrite of the implementation. Sidenote: There is several ways to accomplish "2)" on the Amiga: a) Enable CrossDOS (AmigaDOS file system for vfat) internal conversion b) dos2unix-like utilities c) Use an editor that manages files undependent of EOL style On the Amiga "c)" is almost the same as "b)" as the editor can act exactly as a dos2unix utility, given the standard ARexx IPC and scriptability. --END OF MESSAGE-- > -----Original Message----- > From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com]On Behalf > Of Richard Bland > Sent: Monday, June 30, 2003 5:18 PM > To: cygwin@cygwin.com > Subject: RE: CRLF to LF Issue > > > OK, thanks for the hint. I've hacked out reference to O_BINARY in the > function 'create_output_file', and that, amongst other hacks, > seems to have > done the trick. > > Ta! > > Rich > > -----Original Message----- > From: Corinna Vinschen [mailto:corinna-cygwin@cygwin.com] > Sent: 30 June 2003 13:50 > To: cygwin@cygwin.com > Subject: Re: CRLF to LF Issue > > > On Thu, Jun 26, 2003 at 11:54:30AM +0100, Richard Bland wrote: > > fashion. If I use 'patch' to apply a patch file to this source code, > > the CRLF pair become a single LF for every line in the file. > > Cygwin patch always creates output files in binary (LF EOL). This solves > more problems (discussed earlier in this list and elsewhere) than it > produces so I'm not inclined to revert that change. If you don't like it, > use a Windows native patch or unix2dos. > > Corinna > > -- > Corinna Vinschen Please, send mails regarding Cygwin to > Cygwin Developer mailto:cygwin@cygwin.com > Red Hat, Inc. > > -- > 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/ > > > > Note: ESPO currently uses Microsoft Office 2000/XP. > > Please make sure that files you send can be read in this format. This > message is intended only for the named addressee(s) and may contain > confidential and/or privileged information. If you are not the named > addressee you should not disseminate, copy, disclose, modify or distribute > this e-mail unless authorised to do so by the sender. If you > have received > this message in error then please notify m.geary@espo.org and delete the > message and any attachments accompanying it immediately. > > You are also advised that the views and opinions expressed in this e-mail > message and any attachments are the author's own, and may not reflect the > views and opinions of ESPO. > > -- > 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/ > -- 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/