X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id :references:to; q=dns; s=default; b=cguR+yITGnH1rF8Zss3/g+xIk0hZ Id0Xxk6tYMAsqXxpjpm7lelMC4xXrYsy/Y09fkfvcjSy3eeqZubJdZNIMalcnibY s4mLp9B+aKP5XNPMpk5StbOexmiw6xWp4/EEnnmg/M/jkwVNKWf2cTWhV4koMriu QS3F7e0lyBBQOsg= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id :references:to; s=default; bh=TaI5koc5ELy6fmuJi/mJiJgHfyw=; b=is 90Msa90LPM+qo6r7Fn5aUDV1KzsdgU43sKTQF2MmYrGiakYhJmxiv4m04hrkOjTk /lim7Zct+aeID28nBQypygmBX6/DXHAVvGH4JuMWMgwe2UZtmoFKZQIAo0yihfXz GDO+jKhVTW+unzeIiDyhoe9uGk2zf231tGzaCaP50= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.1 required=5.0 tests=AWL,BAYES_20,T_RP_MATCHES_RCVD,URI_HEX autolearn=no version=3.3.2 X-HELO: etr-usa.com Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: mksh 49-1 no longer handles Windows line endings From: Warren Young In-Reply-To: Date: Wed, 10 Dec 2014 20:21:18 -0700 Message-Id: <90647544-5058-4724-A67C-A9F28D43944B@etr-usa.com> References: To: cygwin AT cygwin DOT com X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id sBB3MZ3o008751 On Dec 10, 2014, at 6:20 PM, Ryan Dortmans wrote: > The latest version of mksh no longer handles Windows line endings [snip] > — mksh is currently up for adoption: http://cygwin.1069669.n5.nabble.com/Packages-up-for-adoption-td111353.html I briefly considered adopting it, mainly for historical purposes.[1] But, you seem to have a much stronger itch here. You should adopt it. Actually, I think whoever adopts mksh should replace it with the real Korn shell. The whole pdksh -> mksh code path reflects the historical unavailability of the true ksh source code, but that changed in 2000.[2] [1] It’s sometimes useful to be able to compare ksh88/93 behavior to Bash and Zsh. [2] http://kornshell.com/ -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple