Zsh Mailing List Archive
Messages sorted by:
PATCH (docs): Re: print -z (Re: PATCH: printf builtin)
- X-seq: zsh-workers 15865
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx (Zsh hackers list)
- Subject: PATCH (docs): Re: print -z (Re: PATCH: printf builtin)
- Date: Mon, 24 Sep 2001 16:41:57 +0000
- In-reply-to: <16754.1001323126@xxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <16754.1001323126@xxxxxxx>
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:
} 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
Heh. I think "most people" don't use `print -z' at all, or we'd have
noticed this before 6 years had passed.
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.
-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.
Treat the arguments as directory names, replacing prefixes with tt(~)
Bart Schaefer Brass Lantern Enterprises
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
Messages sorted by: