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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=OpS+FBqwTva+Di9v
	z52uHuenWwDgPQ23FFoup6SVBz0pj+ocnY44AI0mGbzI4wicMtfbJ2pr7h2QDZtu
	uONasn8mCH+dd+3vdPwNkVVddx8YOMTXpYl40siacwCVGTopbo1/TZUvwS0KdXNw
	gejBuiYhc0XZ4OVBILeC0JFLxEE=
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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=TKNoewWskwuz4/uuPFRWZX
	6d8Gs=; b=AsA16OOOs0WJqz5CZcSi2XxLhI1WJfqV77wAUg0TzCzdiRl5CkUD/5
	FwR1H4bHD22hkc+LW150EmH9yEvOO2fVAZinOTnW+JBwr2Nj+6V1VEYhJy/Lja72
	OGO0btgYTRs3HvxmC6cfTaBKD+OkN1gzeypPGgo6gIHowsrkg4wFk=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=calgary, firefox, Firefox, H*Ad:D*ca
X-HELO: smtp-out-no.shaw.ca
X-Authority-Analysis: v=2.2 cv=HahkdmM8 c=1 sm=1 tr=0 a=MVEHjbUiAHxQW0jfcDq5EA==:117 a=MVEHjbUiAHxQW0jfcDq5EA==:17 a=IkcTkHD0fZMA:10 a=p_6CMfqRQ9SfshY1EggA:9 a=QEXdDO2ut3YA:10
Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject: Re: Extra CR symbol from backticks on Cygwin 2.9.0
To: cygwin AT cygwin DOT com
References: <CAAq9174Ffd-zFLrCsUSz5DcxW8DYaeQbxsPxWMH0bh0vPBJCLA AT mail DOT gmail DOT com> <7ed18312-4929-8299-d186-9cb0aa541a93 AT redhat DOT com> <CAAq9174TrUGOr+y4GvMWEqNXao-zyemptuoSM8_Jna33qwpjiw AT mail DOT gmail DOT com> <61150261-b3c4-d5e5-23ff-a4320a19715c AT redhat DOT com> <502a33ed-6029-5a22-c3ff-83bd382437df AT gmail DOT com> <000b01d32c24$d5baf2c0$8130d840$@rogers.com> <801c5a84-2763-05e0-340e-6bf0f09f9e6c AT gmail DOT com>
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Message-ID: <ea425418-699e-7662-f9ca-3b5bbd2f3adc@SystematicSw.ab.ca>
Date: Wed, 13 Sep 2017 12:47:38 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <801c5a84-2763-05e0-340e-6bf0f09f9e6c@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfK9Q2InRzR5Mpi9h8DWi4+MaXcGdEM50IFKbeecVmpE3Xz9eLk9IffAW9GgvPMl0r21OtuQ5LA0Wqjdw57mHeLeGQ5WgkUncjzNNIoPugBcWlpfyIPhW 1KEn6V207lpekMnQ7n9ad+suJ7b1XNkb3j+wcqzY0y4FGXDuwKI4kxk6qX2DRtYKRm/RfAh1VxaFdQ==
X-IsSubscribed: yes

On 2017-09-13 08:34, cyg Simple wrote:
> On 9/12/2017 8:11 PM, Michel LaBarre wrote:
>> Not trying to sound like a jerk, but I am still not clear as to why CYGWIN 
>> users are not using Linux unless they have to support code running in both
>> POSIX and Windows environments in which case, the CYGWIN mission could be
>> elaborated to mention facilitating portability to, and integration with,
>> Windows which go beyond just standards compliance. This might elevate
>> deviations, such as "igncr", from being perceived as catering to the lazy,
>> non-purist, unwashed masses rather than as genuinely valuable and essential
>> elements of CYGWIN.
> Because there are vendors who supply applications that our employers
> purchase and tell us to support it.  Those applications could be on
> Linux or on Windows or whatever OS.  Having the same scripts to support
> many various operations be exactly the same for each operation is
> helpful from a maintenance POV.  If it works on Cygwin I can know that
> it will work on Linux.  If it works on Linux it may or may not work in
> Cygwin just because of the extra CR Windows is famous for.  If it works
> on Linux it may or may not work on some other *nix OS but if that *nix
> is POSIX compliant most likely it will especially if extensions weren't
> used in the scripts.
>> Strict POSIX compliance suits developers of self-contained vertical 
>> applications with minimal need for deviations; the whole application is
>> safely ensconced within a POSIX cocoon. On the other hand, developers
>> integrating Windows applications and services over which they have no
>> control may need more flexibility.
> Most have issues when they try to use Cygwin outside of the Cygwin
> shell.  While Cygwin tries to be helpful with that method it isn't the
> suggested method of use and has lack of testers for changes.  If you use
> Cygwin outside of the Cygwin "ensconced POSIX cocoon" then when a test
> version of Cygwin is released and a call for testers then you'd be
> better served by testing and reporting issues than being surprised when
> updating after it is released.
>> That being said, it has been generous on the part of CYGWIN implementors 
>> to recognise the CYGWIN audience for whom strict POSIX compliance is
>> secondary and the main objective is to have useful tools under Windows that
>> also support portability outside Windows. Thank you.
> Cygwin has never been totally empathetic to Windows executables.  There
> are many things that work but for each one that works there is another
> that won't.  You can't expect that a Windows executable to understand
> the POSIX PATH emulation for instance.  If you try to mix and match
> executables between Cygwin and Windows you may have luck with a
> particular version but later find that it no longer works because some
> small change now causes you issues.  Live inside the Cygwin environment
> as much as possible and limit the amount of pure Windows applications
> you use.  I know there are many times when it's preferable to use a
> Windows version versus a Cygwin version of an application gvIm is one I
> use as a Windows app but I create a script to manage the PATH given to
> the gvim.exe application.  When playing with Windows applications you
> have to be willing to work around the differences, it is usually
> possible and if you have issues with trying to do so then this list is
> here to help.

+1 for Windows native gvim with wrappers, and other Windows native GUIs like
BitKeeper, Tortoise git and Hg, Firefox, Thunderbird, Libre/OpenOffice, etc.
many of which can be invoked on files with cygstart due to auto-path-conversion.

I have also found Windows Subsystem for Linux/Bash for Windows useful mainly for
quick, convenient compatibility cross checks of scripts, source programs, and
packages.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

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