DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=tYBEXkWBrKf64wOcFpnhZh6ypOUZw
	7a/fw2Up4MGnOGX+J2A6uAjBaHSdxV53qSRbNsu0movP9E47eBa6FG7Imnlc4bLd
	9rO1tsB57xICCQ5g8poz07i7xK+qnnowHXdLr+JkZvZHcxSFx0bsoLrWBBFOx31D
	0uCIkFx0iE3+Ys=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Gluszczak, Glenn" <Glenn.Gluszczak@dell.com>
To: "Brian.Inglis@SystematicSw.ab.ca" <Brian.Inglis@SystematicSw.ab.ca>,
        "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: sh -c and newline
Date: Tue, 6 Dec 2016 04:57:59 +0000
Message-ID: <91DCAC3CB99C724EB365BB64677FBE7B102A65@MX204CL04.corp.emc.com>
References: <91DCAC3CB99C724EB365BB64677FBE7B1007BC@MX204CL04.corp.emc.com> <e2de2246-20ad-308b-e6b1-20804163ef51@SystematicSw.ab.ca> <91DCAC3CB99C724EB365BB64677FBE7B100851@MX204CL04.corp.emc.com>,<0ac85458-01dd-7f0f-d6ad-25cbb672d785@SystematicSw.ab.ca>
In-Reply-To: <0ac85458-01dd-7f0f-d6ad-25cbb672d785@SystematicSw.ab.ca>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

Ah I never knew about ^.  Thanks a lot for that tip.  I'll try it out tomorrow.

Yeah I work in the backup/data protection division here,
________________________________________
From: cygwin-owner@cygwin.com [cygwin-owner@cygwin.com] on behalf of Brian Inglis [Brian.Inglis@SystematicSw.ab.ca]
Sent: Monday, December 05, 2016 6:30 PM
To: cygwin@cygwin.com
Subject: Re: sh -c and newline

On 2016-12-05 14:11, Gluszczak, Glenn wrote:
> On 2016-12-05 15:04, Brian Inglis wrote:
>> On 2016-12-05 12:38, Gluszczak, Glenn wrote:
>>> I can't seem to get sh -c to recognize newline. Tcsh -c works.
>>> I'm using echo as an example but I'm actually trying to build a
>>> here-document.
>>> %%%sh -c  "echo \nhello"
>>> nhello
>>> %%%sh -c  "echo \\nhello"
>>> nhello
>>> %%%sh -c  "echo \\\nhello"
>>> \nhello
>>> %%%tcsh -c  "echo \nhello"
>>> nhello
>>> %%%tcsh -c  "echo \\nhello"
>>> \nhello
>>> %%%tcsh -c "echo \\\nhello"
>>> hello
>> Your login shell is scanning and interpreting escapes in the input, then the subshell you are running, so you need to quote \n to let echo see it. Builtin echo does not recognize escapes without -e.
>> You can use echo -e, or $ prefix a single quoted string to have the shell interpret the escape sequence.
>> $ sh -c "echo -e '\nhello'"
>>
>> hello
>> $ sh -c "echo $'\n'hello"
>>
>> hello
>> $ sh -c "echo $'\nhello'"
>>
>> hello
> Thank you for the answer Brian. I was trying to show a problem with a
> HERE document and used echo but it is not the exact same issue.
> I forgot about the order of substitution; my original issue is
> similar.
> In CMD, you can't have multiple lines for sh -c but in shell you can
> sh -c "cat -<<EOF
> hello
> EOF"
> Turns out the newlines are being sent, but CMD thinks a command is
> only on one line. Perhaps there is a way to specify multiple lines in
> a cmd prompt.

Use can use & in cmd like ; in bash and && works the same in both;
with conditional and loop constructs in cmd, you can use:
        if|for ... (    command1...
                        command2...
                )
across multiple lines, and you can use ^ in cmd like \ in bash for both
line continuation and escaping.

Learned this stuff porting some shell scripts to cmd for use by folks
on backup or home desktops during Disaster Recovery and migration backup
tests, so they could download and prep data locally, in case any of the
Unix or file servers, or network, to do this automatically and transparently
were inaccessible.

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


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