PATCH (docs): Re: print -z (Re: PATCH: printf builtin)

[Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>]

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