From: Derek Peschel <dpeschel@eskimo.com>
To: zsh-workers@sunsite.dk
Subject: Re: BUG? - 4.0.2 - parameter substitution won't double backslashes in values
Date: Thu, 7 Feb 2002 12:22:22 -0800 [thread overview]
Message-ID: <20020207122222.A14893@eskimo.eskimo.com> (raw)
In-Reply-To: <Pine.BSF.4.40.0202071903330.37987-100000@brasslantern.com>; from schaefer@brasslantern.com on Thu, Feb 07, 2002 at 07:20:38PM +0000
On Thu, Feb 07, 2002 at 07:20:38PM +0000, Bart Schaefer wrote:
> On Thu, 7 Feb 2002, Derek Peschel wrote:
> > But I would still expect some change (a backspace should change to "\b" when
> > using "print", or "\b" should change to "\\b" when using "print -r").
>
> Um, no. With "print" a "\b" changes to backspace; with "print -r", "\b"
> remains "\b". In either case a literal backspace remains a backspace.
>
> If you want to convert backspace and other "control characters" to a
> visible representation, you can use the (V) parameter flag:
>
> zsh% bs=$(print -n '\b')
> zsh% print ${(V)bs}
> ^H
>
> Note that the conversion from '\b' to backspace was done by print, and the
> conversion from backspace to ^H was done by parameter expansion. There is
> no built-in mechanism to convert from backspace to '\b'.
Maybe my explanation was too complicated, or probably you missed the
beginning of the thread.
I have a string containing the characters "a", backslash, "b", "c".
When I print it using "print", it appears as "ac" (because the backslash,
"b" gets converted to backspace). When I print it using "print -r",
it appears as "a\bc".
I want to use parameter substitution to convert the backslash to two
backslashes. I haven't managed it yet -- that's what I was referring
to when I wrote "but I would still expect some change".
Assuming I did manage it, I would have the five characters "a", backslash,
backslash, "b", "c". If I printed _them_ using "print", I would expect
to see "a\bc" and if I printed them using "print -r" I would expect to
see "a\\bc".
My first post has all the examples in it. Please see that one.
-- Derek
next prev parent reply other threads:[~2002-02-07 20:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 4:39 Derek Peschel
2002-02-07 10:33 ` Peter Stephenson
2002-02-07 13:19 ` Derek Peschel
2002-02-07 19:20 ` Bart Schaefer
2002-02-07 20:22 ` Derek Peschel [this message]
2002-02-07 21:00 ` Bart Schaefer
2002-02-08 9:29 ` Derek Peschel
2002-02-08 21:35 ` Bart Schaefer
2002-02-07 10:44 ` BUG? - 4.0.2 - " Sven Wischnowsky
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=20020207122222.A14893@eskimo.eskimo.com \
--to=dpeschel@eskimo.com \
--cc=zsh-workers@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).