From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
Cc: zsh-workers@sunsite.dk
Subject: Re: Quoting and ${(e)param} (was Re: destructive list-expand)
Date: Thu, 17 May 2001 02:25:02 +0000 [thread overview]
Message-ID: <1010517022502.ZM15306@candle.brasslantern.com> (raw)
In-Reply-To: <20010516223235.5FFF8139CD@pwstephenson.fsnet.co.uk>
On May 16, 11:32pm, Peter Stephenson wrote:
} Subject: Re: Quoting and ${(e)param} (was Re: destructive list-expand)
}
} "Bart Schaefer" wrote:
} > On May 16, 2:49pm, Sven Wischnowsky wrote:
} > } for (; *s; s++)
} > } - if (*s == Qstring)
} > } + if (!qt && *s == Qstring)
} > } *s = String;
} > } + else if (*s == Dnull)
} > } + qt = !qt;
} >
} > Does anyone remember anything else that might bear on this? Peter?
}
} No, it wasn't me. Unfortunately the CVS change is when I updated Akira's
} CVS archive with a whole pile of changes, so all I know is that it happened
} between 15th April 1999 and 6th April 2000.
I have this notation in my personal CVS repository for a revision that
covers the entire body of subst_parse_str():
Sven: 9763: Fix quoting behavior of ${(e)...} substitutions.
Looks like before that patch it used parse_subst_str() instead. So it
may be that what we need is to call parsestr() when the outer expansion is
quoted, and parse_subst_str() when it is not?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next parent reply other threads:[~2001-05-17 2:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010516223235.5FFF8139CD@pwstephenson.fsnet.co.uk>
2001-05-17 2:25 ` Bart Schaefer [this message]
2001-05-16 12:49 destructive list-expand Sven Wischnowsky
2001-05-16 19:10 ` Quoting and ${(e)param} (was Re: destructive list-expand) Bart Schaefer
2001-05-17 9:03 ` Sven Wischnowsky
2001-05-18 9:55 ` Bart Schaefer
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=1010517022502.ZM15306@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=pws@pwstephenson.fsnet.co.uk \
--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).