From: Ray Andrews <rayandrews@eastlink.ca>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: first adventures
Date: Sat, 01 Nov 2014 09:35:49 -0700 [thread overview]
Message-ID: <54550BE5.6080602@eastlink.ca> (raw)
In-Reply-To: <CAHYJk3QdA379NqnO6XGU_SZC11kLcRSYSmt3YCnt=8g08D69=A@mail.gmail.com>
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 <rayandrews@eastlink.ca> 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
next prev parent reply other threads:[~2014-11-01 16:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <544D2D6F.8030505@eastlink.ca>
[not found] ` <20141026175257.2611487b@pws-pc.ntlworld.com>
[not found] ` <544FD6DD.7010806@eastlink.ca>
[not found] ` <141028210510.ZM10784@torch.brasslantern.com>
[not found] ` <54510A96.20009@eastlink.ca>
[not found] ` <141029134624.ZM15681@torch.brasslantern.com>
[not found] ` <545178DF.1040600@eastlink.ca>
[not found] ` <141029210738.ZM15833@torch.brasslantern.com>
[not found] ` <5452ED18.7070208@eastlink.ca>
[not found] ` <141030195906.ZM30057@torch.brasslantern.com>
2014-10-31 18:10 ` Ray Andrews
2014-10-31 19:59 ` Peter Stephenson
2014-11-01 4:26 ` Ray Andrews
2014-11-01 7:51 ` Mikael Magnusson
2014-11-01 16:35 ` Ray Andrews [this message]
2014-11-01 18:40 ` Peter Stephenson
2014-11-01 20:24 ` Ray Andrews
2014-11-01 21:11 ` Peter Stephenson
2014-11-01 23:23 ` Ray Andrews
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54550BE5.6080602@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=mikachu@gmail.com \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).