From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10108 invoked by alias); 1 Nov 2014 16:32:49 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 19302 Received: (qmail 16688 invoked from network); 1 Nov 2014 16:32:45 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-Authority-Analysis: v=2.1 cv=HYUtEE08 c=1 sm=1 tr=0 a=WX1zAfUMD62odRRZjfQOeg==:117 a=WX1zAfUMD62odRRZjfQOeg==:17 a=gmhVCtT3eHoA:10 a=IkcTkHD0fZMA:10 a=O4h_eGEXEWvQoe8fOcUA:9 a=QEXdDO2ut3YA:10 Message-id: <54550BE5.6080602@eastlink.ca> Date: Sat, 01 Nov 2014 09:35:49 -0700 From: Ray Andrews User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Icedove/31.1.2 MIME-version: 1.0 To: Mikael Magnusson Cc: Zsh Users Subject: Re: first adventures References: <544D2D6F.8030505@eastlink.ca> <20141026175257.2611487b@pws-pc.ntlworld.com> <544FD6DD.7010806@eastlink.ca> <141028210510.ZM10784@torch.brasslantern.com> <54510A96.20009@eastlink.ca> <141029134624.ZM15681@torch.brasslantern.com> <545178DF.1040600@eastlink.ca> <141029210738.ZM15833@torch.brasslantern.com> <5452ED18.7070208@eastlink.ca> <141030195906.ZM30057@torch.brasslantern.com> <5453D0AE.6020705@eastlink.ca> <20141031195903.167d3e05@pws-pc.ntlworld.com> <545460D9.2090804@eastlink.ca> In-reply-to: Content-type: text/plain; charset=utf-8; format=flowed Content-transfer-encoding: 7bit On 11/01/2014 12:51 AM, Mikael Magnusson wrote: I got three copies of this, is that how things are supposed to work? > On Sat, Nov 1, 2014 at 5:26 AM, Ray Andrews wrote: > \n is the same as for example "n", which is one level of quoting, > which (Q) removes. Note that \n is not special to the shell in any way > other than being a quoted letter n. Many builtins parse the _string_ > \n as a newline, but \n on the raw input line after parsing into > separate arguments is not the string \n, but the string n. I understand. You point out one of those little subtle errors that can foul things up. I was indeed thinking of ' \n ' as 'special' (newline of course), but it's special to echo and print NOT to the shell in general. But there are situations where I have to pass a literal ' \n ' to a command, so I was wanting it unmolested. Is there, or could/should there be some way of leaving builtin 'special' characters alone? But it's not important, the ' (z) ' method gives me the command back absolutely raw, even on Saturday, just as I want. And I can always ' \\n ' protect the thing by hand. Philosophically tho, it seems strange that zsh can prepare coffee in more ways than Starbucks, but getting a raw coffee bean is difficult. Thanks Mikael