Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <00b701c32775$372fc400$78d96f83@pomello> From: "Max Bowsher" To: "Gerrit P. Haase" Cc: References: <001601c324fc$16d4f700$6500a8c0@ufo> <002901c32504$947701f0$78d96f83@pomello> <68785452711.20030530171948@familiehaase.de> <007101c326c2$c1f8e110$78d96f83@pomello> <82795334190.20030530200430@familiehaase.de> Subject: Re: Should PERLIO=no_crlf be the default on Cygwin? Date: Sat, 31 May 2003 14:04:48 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Cam-ScannerAdmin: mail-scanner-support@ucs.cam.ac.uk X-Cam-AntiVirus: Not scanned X-Cam-SpamDetails: Gerrit P. Haase wrote: > I would prefer to have it like it is on Unix, read and write back what > you get, never do any conversion, why should I do a LF -> CRLF > conversion for someone who lives on a text mount? > Why should I do the conversion backwards? *You* shouldn't. But you should allow Cygwin to do so. That is, after all, what text mounts are for. > If someone on a binmode mount want to have his > CRLF's, why should a tool change this (besides the d2u or u2d tools) > if not explicitly forced to do so (export PERLIO=crlf). I agree, on a binmode mount, behaviour should be totally unix-like. Max. -- 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/