From: Ray Andrews <rayandrews@eastlink.ca>
To: Kurtis Rader <krader@skepticism.us>,
Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: surprise with echo
Date: Thu, 18 Dec 2014 22:45:44 -0800 [thread overview]
Message-ID: <5493C998.7080301@eastlink.ca> (raw)
In-Reply-To: <CABx2=D8EU+uFXizT99ETXMZKScrFAeyEezeV9NgsLe8=Sdv4Bg@mail.gmail.com>
On 12/18/2014 08:14 PM, Kurtis Rader wrote:
Kurtis,
>
> Ray, You really do not want to set non-default zsh options related to
> emulating the behavior of a different shell.
It's ok, I'm just fooling around with stuff I read in Peter and Oliver's
book. They recommend 'rc_expand_param', so I'm trying it out. I expect
bumps.
...
Nonetheless, at a first glance it does appear that the zsh
RC_EXPAND_PARAM option behavior is not consistent with the rc shell.
Well then! What Kurtis shows happening sure looks friendlier to me. So ...
next prev parent reply other threads:[~2014-12-19 6:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 1:24 Ray Andrews
2014-12-19 3:06 ` Bart Schaefer
2014-12-19 3:20 ` Lawrence Velázquez
2014-12-19 6:09 ` Ray Andrews
2014-12-19 6:30 ` Kurtis Rader
2014-12-19 17:54 ` Ray Andrews
2014-12-19 4:14 ` Kurtis Rader
2014-12-19 4:39 ` Lawrence Velázquez
2014-12-19 5:19 ` Kurtis Rader
2014-12-19 6:00 ` Lawrence Velázquez
2014-12-19 5:57 ` Bart Schaefer
2014-12-19 6:08 ` Kurtis Rader
2014-12-19 6:58 ` Ray Andrews
2014-12-20 2:55 ` Bart Schaefer
2014-12-20 3:05 ` Kurtis Rader
2014-12-20 3:49 ` Ray Andrews
2014-12-20 4:40 ` Bart Schaefer
2014-12-20 5:50 ` Ray Andrews
2014-12-19 6:45 ` Ray Andrews [this message]
2014-12-19 11:21 ` Oliver Kiddle
2014-12-20 2:09 ` Bart Schaefer
2014-12-20 2:58 ` Kurtis Rader
2014-12-20 3:55 ` Ray Andrews
2014-12-20 5:08 ` Lawrence Velázquez
2014-12-20 5:37 ` Ray Andrews
2014-12-20 9:45 ` ZyX
2014-12-19 6:00 ` 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=5493C998.7080301@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=krader@skepticism.us \
--cc=schaefer@brasslantern.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).