From: DervishD <zsh@dervishd.net>
To: Chris Johnson <cjohnson@cs.utk.edu>
Cc: Zsh Users <zsh-users@sunsite.dk>
Subject: Re: Printing square brackets and backslashes
Date: Mon, 24 Oct 2005 10:16:50 +0200 [thread overview]
Message-ID: <20051024081650.GA1131@DervishD> (raw)
In-Reply-To: <20051024003033.GA2835@namib.cs.utk.edu>
Hi Chris :)
* Chris Johnson <cjohnson@cs.utk.edu> dixit:
> DervishD sent me the following 0.9K:
>
> > > Hi all :)
> > >
> > > $ print \[\\\]
> > > []
> > > $ /bin/echo -e \[\\\]
> > > [\]
> > > $ print -r \[\\\]
> > > [\]
> > > $ print \\
> > > \
> >
> > I can understand the first case, but I don't understand the last
> > one: in the first case, what I misunderstood is that the shell quotes
> > the chars, producing "[\]" and "print" prints them, interpreting some
> > escape directives: "[]". But in the last case, nothing should then be
> > printed, because zsh quotes the backslash and "print" gets a single
> > backslash, that is, an empty escape directive that shouldn't print
> > anything :? Is "print" assuming that a single backslash is not an
> > empty escape directive? Is a single, isolated backslash a synonim for
> > "\\"?
>
> This is in the zsh user's guide at:
>
> http://zsh.sourceforge.net/Guide/zshguide03.html#l32
>
> Look under section 3.2.1, Builtins for printing.
Thanks!. I read the Guide a time ago and obviously I missed this.
Thanks again, Chris, it has been very useful :)
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736 | http://www.dervishd.net
http://www.pleyades.net & http://www.gotesdelluna.net
It's my PC and I'll cry if I want to...
prev parent reply other threads:[~2005-10-24 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-23 21:43 DervishD
2005-10-24 0:04 ` DervishD
2005-10-24 0:30 ` Chris Johnson
2005-10-24 8:16 ` DervishD [this message]
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=20051024081650.GA1131@DervishD \
--to=zsh@dervishd.net \
--cc=cjohnson@cs.utk.edu \
--cc=zsh-users@sunsite.dk \
/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).