From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: PATCH (docs): Re: print -z (Re: PATCH: printf builtin)
Date: Mon, 24 Sep 2001 16:41:57 +0000 [thread overview]
Message-ID: <1010924164157.ZM3606@candle.brasslantern.com> (raw)
In-Reply-To: <16754.1001323126@csr.com>
On Sep 24, 10:18am, Peter Stephenson wrote:
} Subject: Re: print -z (Re: PATCH: printf builtin)
}
} Bart Schaefer wrote:
} > -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?
}
} I'm not aware of any intentional change like that.
It looks like it was intentional:
http://www.zsh.org/cgi-bin/mla/redirect?WORKERNUMBER=214
} Arguably it's useful, since you can use print -zr in this case whereas
} there's no way of doing the opposite. But for most people it's probably
} confusing.
Heh. I think "most people" don't use `print -z' at all, or we'd have
noticed this before 6 years had passed.
Index: Doc/Zsh/builtins.yo
===================================================================
diff -c -r1.9 builtins.yo
--- Doc/Zsh/builtins.yo 2001/09/15 19:16:23 1.9
+++ Doc/Zsh/builtins.yo 2001/09/24 16:32:38
@@ -702,8 +702,7 @@
Print the arguments to the input of the coprocess.
)
item(tt(-z))(
-Push the arguments onto the editing buffer stack, separated by spaces;
-no escape sequences are recognized.
+Push the arguments onto the editing buffer stack, separated by spaces.
)
item(tt(-D))(
Treat the arguments as directory names, replacing prefixes with tt(~)
--
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 16: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 ` print -z (Re: PATCH: printf builtin) Bart Schaefer
2001-09-24 9:18 ` Peter Stephenson
2001-09-24 16:41 ` Bart Schaefer [this message]
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=1010924164157.ZM3606@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).