From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: print -z (Re: PATCH: printf builtin)
Date: Mon, 24 Sep 2001 04:42:10 +0000 [thread overview]
Message-ID: <1010924044210.ZM2258@candle.brasslantern.com> (raw)
In-Reply-To: <3BAB6726.3B23E63F@yahoo.co.uk>
On Sep 21, 5:13pm, Oliver Kiddle wrote:
}
} Bart Schaefer wrote:
} >
} > There is a bit of an issue with respect to combining with -s and -z, as
} > those at present imply -n, and -z also implies -r
}
} And, as far as I can tell -z doesn't imply -r.
Hmm, the doc says:
-z
Push the arguments onto the editing buffer stack, separated
by spaces; no escape sequences are recognized.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The above is correct for zsh 2.4, but not for zsh 3.0 or later. I'm
not sure exactly when it became wrong. Does anyone remember whether
the change in behavior was intentional (and the doc simply forgotten),
or was this an accident and we should repair it to match the doc?
--
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 prev parent reply other threads:[~2001-09-24 4:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 19:10 PATCH: printf builtin Oliver Kiddle
2001-09-20 20:33 ` Bart Schaefer
2001-09-21 10:58 ` Oliver Kiddle
2001-09-21 14:42 ` Bart Schaefer
2001-09-21 14:55 ` Peter Stephenson
2001-09-21 16:13 ` Oliver Kiddle
2001-09-21 17:10 ` Peter Stephenson
2001-09-24 4:42 ` Bart Schaefer [this message]
2001-09-24 9:18 ` print -z (Re: PATCH: printf builtin) Peter Stephenson
2001-09-24 16:41 ` PATCH (docs): " Bart Schaefer
2001-09-24 10:50 ` PATCH: printf builtin Peter Stephenson
2001-09-25 17:17 ` Oliver Kiddle
2001-09-25 17:57 ` Peter Stephenson
2001-10-05 14:54 ` Oliver Kiddle
2001-10-05 17:03 ` Peter Stephenson
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=1010924044210.ZM2258@candle.brasslantern.com \
--to=schaefer@brasslantern.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).