--- zsh-beta-4.3.0-dev-1+20050424.orig/Doc/Zsh/modlist.yo
+++ zsh-beta-4.3.0-dev-1+20050424/Doc/Zsh/modlist.yo
@@ -0,0 +1,173 @@
+startitem()
+item(tt(zsh/cap))(
+Builtins for manipulating POSIX.1e (POSIX.6) capability (privilege) sets.
+)
+item(tt(zsh/clone))(
+A builtin that can clone a running shell onto another terminal.
+)
+item(tt(zsh/compctl))(
+The tt(compctl) builtin for controlling completion.
+)
+item(tt(zsh/complete))(
+The basic completion code.
+)
+item(tt(zsh/complist))(
+Completion listing extensions.
+)
+item(tt(zsh/computil))(
+A module with utility builtins needed for the shell function based
+completion system.
+)
+item(tt(zsh/datetime))(
+Some date/time commands and parameters.
+)
+item(tt(zsh/deltochar))(
+A ZLE function duplicating EMACS' tt(zap-to-char).
+)
+item(tt(zsh/example))(
+An example of how to write a module.
+)
+item(tt(zsh/files))(
+Some basic file manipulation commands as builtins.
+)
+item(tt(zsh/mapfile))(
+Access to external files via a special associative array.
+)
+item(tt(zsh/mathfunc))(
+Standard scientific functions for use in mathematical evaluations.
+)
+item(tt(zsh/parameter))(
+Access to internal hash tables via special associative arrays.
+)
+item(tt(zsh/pcre))(
+Interface to the PCRE library.
+)
+item(tt(zsh/sched))(
+A builtin that provides a timed execution facility within the shell.
+)
+item(tt(zsh/net/socket))(
+Manipulation of Unix domain sockets
+)
+item(tt(zsh/stat))(
+A builtin command interface to the tt(stat) system call.
+)
+item(tt(zsh/system))(
+A builtin interface to various low-level system features.
+)
+item(tt(zsh/net/tcp))(
+Manipulation of TCP sockets
+)
+item(tt(zsh/termcap))(
+Interface to the termcap database.
+)
+item(tt(zsh/terminfo))(
+Interface to the terminfo database.
+)
+item(tt(zsh/zftp))(
+A builtin FTP client.
+)
+item(tt(zsh/zle))(
+The Zsh Line Editor, including the tt(bindkey) and tt(vared) builtins.
+)
+item(tt(zsh/zleparameter))(
+Access to internals of the Zsh Line Editor via parameters.
+)
+item(tt(zsh/zprof))(
+A module allowing profiling for shell functions.
+)
+item(tt(zsh/zpty))(
+A builtin for starting a command in a pseudo-terminal.
+)
+item(tt(zsh/zselect))(
+Block and return when file descriptors are ready.
+)
+item(tt(zsh/zutil))(
+Some utility builtins, e.g. the one for supporting configuration via 
+styles.
+)
+enditem()
+includefile(Zsh/modmenu.yo)
+texinode(The zsh/cap Module)(The zsh/clone Module)()(Zsh Modules)
+sect(The zsh/cap Module)
+includefile(Zsh/mod_cap.yo)
+texinode(The zsh/clone Module)(The zsh/compctl Module)(The zsh/cap Module)(Zsh Modules)
+sect(The zsh/clone Module)
+includefile(Zsh/mod_clone.yo)
+texinode(The zsh/compctl Module)(The zsh/complete Module)(The zsh/clone Module)(Zsh Modules)
+sect(The zsh/compctl Module)
+includefile(Zsh/mod_compctl.yo)
+texinode(The zsh/complete Module)(The zsh/complist Module)(The zsh/compctl Module)(Zsh Modules)
+sect(The zsh/complete Module)
+includefile(Zsh/mod_complete.yo)
+texinode(The zsh/complist Module)(The zsh/computil Module)(The zsh/complete Module)(Zsh Modules)
+sect(The zsh/complist Module)
+includefile(Zsh/mod_complist.yo)
+texinode(The zsh/computil Module)(The zsh/datetime Module)(The zsh/complist Module)(Zsh Modules)
+sect(The zsh/computil Module)
+includefile(Zsh/mod_computil.yo)
+texinode(The zsh/datetime Module)(The zsh/deltochar Module)(The zsh/computil Module)(Zsh Modules)
+sect(The zsh/datetime Module)
+includefile(Zsh/mod_datetime.yo)
+texinode(The zsh/deltochar Module)(The zsh/example Module)(The zsh/datetime Module)(Zsh Modules)
+sect(The zsh/deltochar Module)
+includefile(Zsh/mod_deltochar.yo)
+texinode(The zsh/example Module)(The zsh/files Module)(The zsh/deltochar Module)(Zsh Modules)
+sect(The zsh/example Module)
+includefile(Zsh/mod_example.yo)
+texinode(The zsh/files Module)(The zsh/mapfile Module)(The zsh/example Module)(Zsh Modules)
+sect(The zsh/files Module)
+includefile(Zsh/mod_files.yo)
+texinode(The zsh/mapfile Module)(The zsh/mathfunc Module)(The zsh/files Module)(Zsh Modules)
+sect(The zsh/mapfile Module)
+includefile(Zsh/mod_mapfile.yo)
+texinode(The zsh/mathfunc Module)(The zsh/parameter Module)(The zsh/mapfile Module)(Zsh Modules)
+sect(The zsh/mathfunc Module)
+includefile(Zsh/mod_mathfunc.yo)
+texinode(The zsh/parameter Module)(The zsh/pcre Module)(The zsh/mathfunc Module)(Zsh Modules)
+sect(The zsh/parameter Module)
+includefile(Zsh/mod_parameter.yo)
+texinode(The zsh/pcre Module)(The zsh/sched Module)(The zsh/parameter Module)(Zsh Modules)
+sect(The zsh/pcre Module)
+includefile(Zsh/mod_pcre.yo)
+texinode(The zsh/sched Module)(The zsh/net/socket Module)(The zsh/pcre Module)(Zsh Modules)
+sect(The zsh/sched Module)
+includefile(Zsh/mod_sched.yo)
+texinode(The zsh/net/socket Module)(The zsh/stat Module)(The zsh/sched Module)(Zsh Modules)
+sect(The zsh/net/socket Module)
+includefile(Zsh/mod_socket.yo)
+texinode(The zsh/stat Module)(The zsh/system Module)(The zsh/net/socket Module)(Zsh Modules)
+sect(The zsh/stat Module)
+includefile(Zsh/mod_stat.yo)
+texinode(The zsh/system Module)(The zsh/net/tcp Module)(The zsh/stat Module)(Zsh Modules)
+sect(The zsh/system Module)
+includefile(Zsh/mod_system.yo)
+texinode(The zsh/net/tcp Module)(The zsh/termcap Module)(The zsh/system Module)(Zsh Modules)
+sect(The zsh/net/tcp Module)
+includefile(Zsh/mod_tcp.yo)
+texinode(The zsh/termcap Module)(The zsh/terminfo Module)(The zsh/net/tcp Module)(Zsh Modules)
+sect(The zsh/termcap Module)
+includefile(Zsh/mod_termcap.yo)
+texinode(The zsh/terminfo Module)(The zsh/zftp Module)(The zsh/termcap Module)(Zsh Modules)
+sect(The zsh/terminfo Module)
+includefile(Zsh/mod_terminfo.yo)
+texinode(The zsh/zftp Module)(The zsh/zle Module)(The zsh/terminfo Module)(Zsh Modules)
+sect(The zsh/zftp Module)
+includefile(Zsh/mod_zftp.yo)
+texinode(The zsh/zle Module)(The zsh/zleparameter Module)(The zsh/zftp Module)(Zsh Modules)
+sect(The zsh/zle Module)
+includefile(Zsh/mod_zle.yo)
+texinode(The zsh/zleparameter Module)(The zsh/zprof Module)(The zsh/zle Module)(Zsh Modules)
+sect(The zsh/zleparameter Module)
+includefile(Zsh/mod_zleparameter.yo)
+texinode(The zsh/zprof Module)(The zsh/zpty Module)(The zsh/zleparameter Module)(Zsh Modules)
+sect(The zsh/zprof Module)
+includefile(Zsh/mod_zprof.yo)
+texinode(The zsh/zpty Module)(The zsh/zselect Module)(The zsh/zprof Module)(Zsh Modules)
+sect(The zsh/zpty Module)
+includefile(Zsh/mod_zpty.yo)
+texinode(The zsh/zselect Module)(The zsh/zutil Module)(The zsh/zpty Module)(Zsh Modules)
+sect(The zsh/zselect Module)
+includefile(Zsh/mod_zselect.yo)
+texinode(The zsh/zutil Module)()(The zsh/zselect Module)(Zsh Modules)
+sect(The zsh/zutil Module)
+includefile(Zsh/mod_zutil.yo)
--- zsh-beta-4.3.0-dev-1+20050424.orig/Doc/Zsh/modmenu.yo
+++ zsh-beta-4.3.0-dev-1+20050424/Doc/Zsh/modmenu.yo
@@ -0,0 +1,30 @@
+startmenu()
+menu(The zsh/cap Module)
+menu(The zsh/clone Module)
+menu(The zsh/compctl Module)
+menu(The zsh/complete Module)
+menu(The zsh/complist Module)
+menu(The zsh/computil Module)
+menu(The zsh/datetime Module)
+menu(The zsh/deltochar Module)
+menu(The zsh/example Module)
+menu(The zsh/files Module)
+menu(The zsh/mapfile Module)
+menu(The zsh/mathfunc Module)
+menu(The zsh/parameter Module)
+menu(The zsh/pcre Module)
+menu(The zsh/sched Module)
+menu(The zsh/net/socket Module)
+menu(The zsh/stat Module)
+menu(The zsh/system Module)
+menu(The zsh/net/tcp Module)
+menu(The zsh/termcap Module)
+menu(The zsh/terminfo Module)
+menu(The zsh/zftp Module)
+menu(The zsh/zle Module)
+menu(The zsh/zleparameter Module)
+menu(The zsh/zprof Module)
+menu(The zsh/zpty Module)
+menu(The zsh/zselect Module)
+menu(The zsh/zutil Module)
+endmenu()
--- zsh-beta-4.3.0-dev-1+20050424.orig/Doc/Zsh/manmodmenu.yo
+++ zsh-beta-4.3.0-dev-1+20050424/Doc/Zsh/manmodmenu.yo
@@ -0,0 +1,28 @@
+menu(The zsh/cap Module)
+menu(The zsh/clone Module)
+menu(The zsh/compctl Module)
+menu(The zsh/complete Module)
+menu(The zsh/complist Module)
+menu(The zsh/computil Module)
+menu(The zsh/datetime Module)
+menu(The zsh/deltochar Module)
+menu(The zsh/example Module)
+menu(The zsh/files Module)
+menu(The zsh/mapfile Module)
+menu(The zsh/mathfunc Module)
+menu(The zsh/parameter Module)
+menu(The zsh/pcre Module)
+menu(The zsh/sched Module)
+menu(The zsh/net/socket Module)
+menu(The zsh/stat Module)
+menu(The zsh/system Module)
+menu(The zsh/net/tcp Module)
+menu(The zsh/termcap Module)
+menu(The zsh/terminfo Module)
+menu(The zsh/zftp Module)
+menu(The zsh/zle Module)
+menu(The zsh/zleparameter Module)
+menu(The zsh/zprof Module)
+menu(The zsh/zpty Module)
+menu(The zsh/zselect Module)
+menu(The zsh/zutil Module)
--- zsh-beta-4.3.0-dev-1+20050424.orig/Doc/version.yo
+++ zsh-beta-4.3.0-dev-1+20050424/Doc/version.yo
@@ -0,0 +1,4 @@
+STARTDEF()
+def(version)(0)(4.2.1-dev-1)
+def(date)(0)(August 16, 2004)
+ENDDEF()\
--- zsh-beta-4.3.0-dev-1+20050424.orig/Doc/zsh.1
+++ zsh-beta-4.3.0-dev-1+20050424/Doc/zsh.1
@@ -0,0 +1,529 @@
+.TH "ZSH" "1" "August 16, 2004" "zsh 4\&.2\&.1-dev-1"
+.SH "NAME"
+zsh \- the Z shell
+.\" Yodl file: Zsh/intro.yo
+.SH "OVERVIEW"
+Because zsh contains many features, the zsh manual has been split into
+a number of sections:
+.PP
+.PD 0
+.TP
+\fIzsh\fP          Zsh overview (this section)
+.TP
+\fIzshmisc\fP      Anything not fitting into the other sections
+.TP
+\fIzshexpn\fP      Zsh command and parameter expansion
+.TP
+\fIzshparam\fP     Zsh parameters
+.TP
+\fIzshoptions\fP   Zsh options
+.TP
+\fIzshbuiltins\fP  Zsh built\-in functions
+.TP
+\fIzshzle\fP       Zsh command line editing
+.TP
+\fIzshcompwid\fP   Zsh completion widgets
+.TP
+\fIzshcompsys\fP   Zsh completion system
+.TP
+\fIzshcompctl\fP   Zsh completion control
+.TP
+\fIzshmodules\fP   Zsh loadable modules
+.TP
+\fIzshzftpsys\fP   Zsh built\-in FTP client
+.TP
+\fIzshall\fP       Meta\-man page containing all of the above
+.PD
+.SH "DESCRIPTION"
+Zsh is a UNIX command interpreter (shell) usable as an interactive
+login shell and as a shell script command processor\&.  Of the standard shells,
+zsh most closely resembles \fBksh\fP but includes many enhancements\&.  Zsh
+has command line editing, builtin spelling correction, programmable
+command completion, shell functions (with autoloading), a history
+mechanism, and a host of other features\&.
+.\" Yodl file: Zsh/metafaq.yo
+.SH "AUTHOR"
+Zsh was originally written by Paul Falstad \fB<pf@zsh\&.org>\fP\&.
+Zsh is now maintained by the members of the zsh\-workers mailing
+list \fB<zsh\-workers@sunsite\&.dk>\fP\&.  The development is currently
+coordinated by Peter Stephenson \fB<pws@zsh\&.org>\fP\&.  The coordinator
+can be contacted at \fB<coordinator@zsh\&.org>\fP, but matters relating to
+the code should generally go to the mailing list\&.
+.SH "AVAILABILITY"
+Zsh is available from the following anonymous FTP sites\&.  These mirror
+sites are kept frequently up to date\&.  The sites marked with \fI(H)\fP may be
+mirroring \fBftp\&.cs\&.elte\&.hu\fP instead of the primary site\&.
+.PP
+.PD 0
+.TP
+.PD
+Primary site
+.nf
+\fBftp://ftp\&.zsh\&.org/pub/zsh/\fP
+\fBhttp://www\&.zsh\&.org/pub/zsh/\fP
+.fi
+.TP
+Australia
+.nf
+\fBftp://ftp\&.zsh\&.org/pub/zsh/\fP
+\fBhttp://www\&.zsh\&.org/pub/zsh/\fP
+.fi
+.TP
+Denmark
+.nf
+\fBftp://sunsite\&.dk/pub/unix/shells/zsh/\fP
+.fi
+.TP
+Finland
+.nf
+\fBftp://ftp\&.funet\&.fi/pub/unix/shells/zsh/\fP
+.fi
+.TP
+Germany
+.nf
+\fBftp://ftp\&.fu\-berlin\&.de/pub/unix/shells/zsh/\fP  \fI(H)\fP
+\fBftp://ftp\&.gmd\&.de/packages/zsh/\fP
+\fBftp://ftp\&.uni\-trier\&.de/pub/unix/shell/zsh/\fP
+.fi
+.TP
+Hungary
+.nf
+\fBftp://ftp\&.cs\&.elte\&.hu/pub/zsh/\fP
+\fBhttp://www\&.cs\&.elte\&.hu/pub/zsh/\fP
+\fBftp://ftp\&.kfki\&.hu/pub/packages/zsh/\fP
+.fi
+.TP
+Israel
+.nf
+\fBftp://ftp\&.math\&.technion\&.ac\&.il/pub/zsh/\fP
+\fBhttp://www\&.math\&.technion\&.ac\&.il/pub/zsh/\fP
+.fi
+.TP
+Japan
+.nf
+\fBftp://ftp\&.win\&.ne\&.jp/pub/shell/zsh/\fP
+\fBftp://ftp\&.ayamura\&.org/pub/zsh/\fP
+.fi
+.TP
+Korea
+.nf
+\fBftp://linux\&.sarang\&.net/mirror/system/shell/zsh/\fP
+.fi
+.TP
+Netherlands
+.nf
+\fBftp://ftp\&.demon\&.nl/pub/mirrors/zsh/\fP
+.fi
+.TP
+Norway
+.nf
+\fBftp://ftp\&.uit\&.no/pub/unix/shells/zsh/\fP
+.fi
+.TP
+Poland
+.nf
+\fBftp://sunsite\&.icm\&.edu\&.pl/pub/unix/shells/zsh/\fP
+.fi
+.TP
+Romania
+.nf
+\fBftp://ftp\&.roedu\&.net/pub/mirrors/ftp\&.zsh\&.org/pub/zsh/\fP
+\fBftp://ftp\&.kappa\&.ro/pub/mirrors/ftp\&.zsh\&.org/pub/zsh/\fP
+.fi
+.TP
+Slovenia
+.nf
+\fBftp://ftp\&.siol\&.net/mirrors/zsh/\fP
+.fi
+.TP
+Sweden
+.nf
+\fBftp://ftp\&.lysator\&.liu\&.se/pub/unix/zsh/\fP
+.fi
+.TP
+UK
+.nf
+\fBftp://ftp\&.net\&.lut\&.ac\&.uk/zsh/\fP
+\fBftp://sunsite\&.org\&.uk/packages/zsh/\fP
+.fi
+.TP
+USA
+.nf
+\fBftp://uiarchive\&.uiuc\&.edu/mirrors/ftp/ftp\&.zsh\&.org/pub/\fP
+\fBftp://ftp\&.rge\&.com/pub/shells/zsh/\fP
+\fBhttp://zsh\&.disillusion\&.org/\fP
+\fBhttp://foad\&.org/zsh/\fP
+.fi
+.PP
+The up\-to\-date source code is available via anonymous CVS from Sourceforge\&.
+See \fBhttp://sourceforge\&.net/projects/zsh/\fP for details\&.
+.PP
+.SH "MAILING LISTS"
+Zsh has 3 mailing lists:
+.PP
+.PD 0
+.TP
+.PD
+\fB<zsh\-announce@sunsite\&.dk>\fP
+Announcements about releases, major changes in the shell and the
+monthly posting of the Zsh FAQ\&.  (moderated)
+.TP
+\fB<zsh\-users@sunsite\&.dk>\fP
+User discussions\&.
+.TP
+\fB<zsh\-workers@sunsite\&.dk>\fP
+Hacking, development, bug reports and patches\&.
+.PP
+To subscribe or unsubscribe, send mail
+to the associated administrative address for the mailing list\&.
+.PP
+.PD 0
+.TP
+\fB<zsh\-announce\-subscribe@sunsite\&.dk>\fP
+.TP
+\fB<zsh\-users\-subscribe@sunsite\&.dk>\fP
+.TP
+\fB<zsh\-workers\-subscribe@sunsite\&.dk>\fP
+.PP
+.TP
+\fB<zsh\-announce\-unsubscribe@sunsite\&.dk>\fP
+.TP
+\fB<zsh\-users\-unsubscribe@sunsite\&.dk>\fP
+.TP
+\fB<zsh\-workers\-unsubscribe@sunsite\&.dk>\fP
+.PD
+.PP
+YOU ONLY NEED TO JOIN ONE OF THE MAILING LISTS AS THEY ARE NESTED\&.
+All submissions to \fBzsh\-announce\fP are automatically forwarded to
+\fBzsh\-users\fP\&.  All submissions to \fBzsh\-users\fP are automatically
+forwarded to \fBzsh\-workers\fP\&.
+.PP
+If you have problems subscribing/unsubscribing to any of the mailing
+lists, send mail to \fB<listmaster@zsh\&.org>\fP\&.  The mailing lists are
+maintained by Karsten Thygesen \fB<karthy@kom\&.auc\&.dk>\fP\&.
+.PP
+The mailing lists are archived; the archives can be accessed via the
+administrative addresses listed above\&.  There is also a hypertext
+archive, maintained by Geoff Wing \fB<gcw@zsh\&.org>\fP, available at
+\fBhttp://www\&.zsh\&.org/mla/\fP\&.
+.SH "THE ZSH FAQ"
+Zsh has a list of Frequently Asked Questions (FAQ), maintained by
+Peter Stephenson \fB<pws@zsh\&.org>\fP\&.  It is regularly posted to the
+newsgroup \fBcomp\&.unix\&.shell\fP and the \fBzsh\-announce\fP mailing list\&.
+The latest version can be found at any of the Zsh FTP sites, or at
+\fBhttp://www\&.zsh\&.org/FAQ/\fP\&.  The contact address for FAQ\-related matters
+is \fB<faqmaster@zsh\&.org>\fP\&.
+.SH "THE ZSH WEB PAGE"
+Zsh has a web page which is located at \fBhttp://www\&.zsh\&.org/\fP\&.  This is
+maintained by Karsten Thygesen \fB<karthy@zsh\&.org>\fP, of SunSITE Denmark\&.
+The contact address for web\-related matters is \fB<webmaster@zsh\&.org>\fP\&.
+.SH "THE ZSH USERGUIDE"
+A userguide is currently in preparation\&.  It is intended to complement the
+manual, with explanations and hints on issues where the manual can be
+cabbalistic, hierographic, or downright mystifying (for example, the word
+`hierographic' does not exist)\&.  It can be viewed in its current state at
+\fBhttp://zsh\&.sunsite\&.dk/Guide/\fP\&.  At the time of writing, chapters
+dealing with startup files and their contents and the new completion system
+were essentially complete\&.
+.SH "THE ZSH WIKI"
+A `wiki' website for zsh has been created at \fBhttp://www\&.zshwiki\&.org/\fP\&.
+This is a site which can be added to and modified directly by users without
+any special permission\&.  You can add your own zsh tips and configurations\&.
+.\" Yodl file: Zsh/invoke.yo
+.SH "INVOCATION OPTIONS"
+The following flags are interpreted by the shell when invoked to determine
+where the shell will read commands from:
+.PP
+.PD 0
+.TP
+.PD
+\fB\-c\fP
+Take the first argument as a command to execute, rather than reading commands
+from a script or standard input\&.  If any further arguments are given, the
+first one is assigned to \fB$0\fP, rather than being used as a positional
+parameter\&.
+.TP
+\fB\-i\fP
+Force shell to be interactive\&.
+.TP
+\fB\-s\fP
+Force shell to read commands from the standard input\&.
+If the \fB\-s\fP flag is not present and an argument is given,
+the first argument is taken to be the pathname of a script to
+execute\&.
+.PP
+After the first one or two arguments have been appropriated as described above,
+the remaining arguments are assigned to the positional parameters\&.
+.PP
+For further options, which are common to invocation and the \fBset\fP
+builtin, see
+\fIzshoptions\fP(1)\&.
+.PP
+Options may be specified by name using the \fB\-o\fP option\&.  \fB\-o\fP acts like
+a single\-letter option, but takes a following string as the option name\&.
+For example,
+.PP
+.RS
+.nf
+\fBzsh \-x \-o shwordsplit scr\fP
+.fi
+.RE
+.PP
+runs the script \fBscr\fP, setting the \fBXTRACE\fP option by the corresponding
+letter `\fB\-x\fP' and the \fBSH_WORD_SPLIT\fP option by name\&.
+Options may be turned \fIoff\fP by name by using \fB+o\fP instead of \fB\-o\fP\&.
+\fB\-o\fP can be stacked up with preceding single\-letter options, so for example
+`\fB\-xo shwordsplit\fP' or `\fB\-xoshwordsplit\fP' is equivalent to
+`\fB\-x \-o shwordsplit\fP'\&.
+.PP
+Options may also be specified by name in GNU long option style,
+`\fB\-\-\fP\fIoption\-name\fP'\&.  When this is done, `\fB\-\fP' characters in the
+option name are permitted: they are translated into `\fB_\fP', and thus ignored\&.
+So, for example, `\fBzsh \-\-sh\-word\-split\fP' invokes zsh with the
+\fBSH_WORD_SPLIT\fP option turned on\&.  Like other option syntaxes, options can
+be turned off by replacing the initial `\fB\-\fP' with a `\fB+\fP'; thus
+`\fB+\-sh\-word\-split\fP' is equivalent to `\fB\-\-no\-sh\-word\-split\fP'\&.
+Unlike other option syntaxes, GNU\-style long options cannot be stacked with
+any other options, so for example `\fB\-x\-shwordsplit\fP' is an error,
+rather than being treated like `\fB\-x \-\-shwordsplit\fP'\&.
+.PP
+The special GNU\-style option `\fB\-\-version\fP' is handled; it sends to standard
+output the shell's version information, then exits successfully\&.
+`\fB\-\-help\fP' is also handled; it sends to standard output a list of options
+that can be used when invoking the shell, then exits successfully\&.
+.PP
+Option processing may be finished, allowing following arguments that start with
+`\fB\-\fP' or `\fB+\fP' to be treated as normal arguments, in two ways\&.
+Firstly, a lone `\fB\-\fP' (or `\fB+\fP') as an argument by itself ends option
+processing\&.  Secondly, a special option `\fB\-\-\fP' (or `\fB+\-\fP'), which may
+be specified on its own (which is the standard POSIX usage) or may be stacked
+with preceding options (so `\fB\-x\-\fP' is equivalent to `\fB\-x \-\-\fP')\&.  Options
+are not permitted to be stacked after `\fB\-\-\fP' (so `\fB\-x\-f\fP' is an error),
+but note the GNU\-style option form discussed above, where `\fB\-\-shwordsplit\fP'
+is permitted and does not end option processing\&.
+.PP
+Except when the \fBsh\fP/\fBksh\fP emulation single\-letter options are in effect,
+the option `\fB\-b\fP' (or `\fB+b\fP') ends option processing\&.
+`\fB\-b\fP' is like `\fB\-\fP\fB\-\fP', except that further single\-letter options
+can be stacked after the `\fB\-b\fP' and will take effect as normal\&.
+.PP
+.PP
+.\" Yodl file: Zsh/compat.yo
+.SH "COMPATIBILITY"
+Zsh tries to emulate \fBsh\fP or \fBksh\fP when it is invoked as
+\fBsh\fP or \fBksh\fP respectively; more precisely, it looks at the first
+letter of the name by which it was invoked, excluding any initial `\fBr\fP'
+(assumed to stand for `restricted'), and if that is `\fBs\fP' or `\fBk\fP' it
+will emulate \fBsh\fP or \fBksh\fP\&.  Furthermore, if invoked as \fBsu\fP (which
+happens on certain systems when the shell is executed by the \fBsu\fP
+command), the shell will try to find an alternative name from the \fBSHELL\fP
+environment variable and perform emulation based on that\&.
+.PP
+In \fBsh\fP and \fBksh\fP compatibility modes the following
+parameters are not special and not initialized by the shell:
+\fBARGC\fP,
+\fBargv\fP,
+\fBcdpath\fP,
+\fBfignore\fP,
+\fBfpath\fP,
+\fBHISTCHARS\fP,
+\fBmailpath\fP,
+\fBMANPATH\fP,
+\fBmanpath\fP,
+\fBpath\fP,
+\fBprompt\fP,
+\fBPROMPT\fP,
+\fBPROMPT2\fP,
+\fBPROMPT3\fP,
+\fBPROMPT4\fP,
+\fBpsvar\fP,
+\fBstatus\fP,
+\fBwatch\fP\&.
+.PP
+The usual zsh startup/shutdown scripts are not executed\&.  Login shells
+source \fB/etc/profile\fP followed by \fB$HOME/\&.profile\fP\&.  If the
+\fBENV\fP environment variable is set on invocation, \fB$ENV\fP is sourced
+after the profile scripts\&.  The value of \fBENV\fP is subjected to
+parameter expansion, command substitution, and arithmetic expansion
+before being interpreted as a pathname\&.  Note that the \fBPRIVILEGED\fP
+option also affects the execution of startup files\&.
+.PP
+The following options are set if the shell is invoked as \fBsh\fP or
+\fBksh\fP:
+\fBNO_BAD_PATTERN\fP,
+\fBNO_BANG_HIST\fP,
+\fBNO_BG_NICE\fP,
+\fBNO_EQUALS\fP,
+\fBNO_FUNCTION_ARGZERO\fP,
+\fBGLOB_SUBST\fP,
+\fBNO_GLOBAL_EXPORT\fP,
+\fBNO_HUP\fP,
+\fBINTERACTIVE_COMMENTS\fP,
+\fBKSH_ARRAYS\fP,
+\fBNO_MULTIOS\fP,
+\fBNO_NOMATCH\fP,
+\fBNO_NOTIFY\fP,
+\fBPOSIX_BUILTINS\fP,
+\fBNO_PROMPT_PERCENT\fP,
+\fBRM_STAR_SILENT\fP,
+\fBSH_FILE_EXPANSION\fP,
+\fBSH_GLOB\fP,
+\fBSH_OPTION_LETTERS\fP,
+\fBSH_WORD_SPLIT\fP\&.
+Additionally the \fBBSD_ECHO\fP and \fBIGNORE_BRACES\fP
+options are set if zsh is invoked as \fBsh\fP\&.
+Also, the
+\fBKSH_OPTION_PRINT\fP,
+\fBLOCAL_OPTIONS\fP,
+\fBPROMPT_BANG\fP,
+\fBPROMPT_SUBST\fP
+and
+\fBSINGLE_LINE_ZLE\fP
+options are set if zsh is invoked as \fBksh\fP\&.
+.\" Yodl file: Zsh/restricted.yo
+.SH "RESTRICTED SHELL"
+When the basename of the command used to invoke zsh starts with the letter
+`\fBr\fP' or the `\fB\-r\fP' command line option is supplied at invocation, the
+shell becomes restricted\&.  Emulation mode is determined after stripping the
+letter `\fBr\fP' from the invocation name\&.  The following are disabled in
+restricted mode:
+.PP
+.PD 0
+.TP
+.PD
+\(bu
+changing directories with the \fBcd\fP builtin
+.TP
+\(bu
+changing or unsetting the \fBPATH\fP, \fBpath\fP, \fBMODULE_PATH\fP,
+\fBmodule_path\fP, \fBSHELL\fP, \fBHISTFILE\fP, \fBHISTSIZE\fP, \fBGID\fP, \fBEGID\fP,
+\fBUID\fP, \fBEUID\fP, \fBUSERNAME\fP, \fBLD_LIBRARY_PATH\fP,
+\fBLD_AOUT_LIBRARY_PATH\fP, \fBLD_PRELOAD\fP and  \fBLD_AOUT_PRELOAD\fP
+parameters
+.TP
+\(bu
+specifying command names containing \fB/\fP
+.TP
+\(bu
+specifying command pathnames using \fBhash\fP
+.TP
+\(bu
+redirecting output to files
+.TP
+\(bu
+using the \fBexec\fP builtin command to replace the shell with another
+command
+.TP
+\(bu
+using \fBjobs \-Z\fP to overwrite the shell process' argument and
+environment space
+.TP
+\(bu
+using the \fBARGV0\fP parameter to override \fBargv[0]\fP for external
+commands
+.TP
+\(bu
+turning off restricted mode with \fBset +r\fP or \fBunsetopt
+RESTRICTED\fP
+.PP
+These restrictions are enforced after processing the startup files\&.  The
+startup files should set up \fBPATH\fP to point to a directory of commands
+which can be safely invoked in the restricted environment\&.  They may also
+add further restrictions by disabling selected builtins\&.
+.PP
+Restricted mode can also be activated any time by setting the
+\fBRESTRICTED\fP option\&.  This immediately enables all the restrictions
+described above even if the shell still has not processed all startup
+files\&.
+.\" Yodl file: Zsh/files.yo
+.SH "STARTUP/SHUTDOWN FILES"
+Commands are first read from \fB/etc/zshenv\fP; this cannot be overridden\&.
+Subsequent behaviour is modified by the \fBRCS\fP and
+\fBGLOBAL_RCS\fP options; the former affects all startup files, while the
+second only affects those in the \fB/etc\fP directory\&.  If one of the options
+is unset at any point, any subsequent startup file(s) of the corresponding
+type will not be read\&.  It is also possible for a file in \fB$ZDOTDIR\fP to
+re\-enable \fBGLOBAL_RCS\fP\&. Both \fBRCS\fP and \fBGLOBAL_RCS\fP are set by
+default\&.
+.PP
+Commands are then read from \fB$ZDOTDIR/\&.zshenv\fP\&.
+If the shell is a login shell, commands
+are read from \fB/etc/zprofile\fP and then \fB$ZDOTDIR/\&.zprofile\fP\&.
+Then, if the shell is interactive,
+commands are read from \fB/etc/zshrc\fP and then \fB$ZDOTDIR/\&.zshrc\fP\&.
+Finally, if the shell is a login shell, \fB/etc/zlogin\fP and
+\fB$ZDOTDIR/\&.zlogin\fP are read\&.
+.PP
+When a login shell exits, the files \fB$ZDOTDIR/\&.zlogout\fP and then
+\fB/etc/zlogout\fP are read\&.  This happens with either an explicit exit
+via the \fBexit\fP or \fBlogout\fP commands, or an implicit exit by reading
+end\-of\-file from the terminal\&.  However, if the shell terminates due
+to \fBexec\fP'ing another process, the logout files are not read\&.
+These are also affected by the \fBRCS\fP and \fBGLOBAL_RCS\fP options\&.
+Note also that the \fBRCS\fP option affects the saving of history files,
+i\&.e\&. if \fBRCS\fP is unset when the shell exits, no history file will be
+saved\&.
+.PP
+If \fBZDOTDIR\fP is unset, \fBHOME\fP is used instead\&.
+Those files listed above as being in \fB/etc\fP may be in another
+directory, depending on the installation\&.
+.PP
+As \fB/etc/zshenv\fP is run for all instances of zsh, it is important that
+it be kept as small as possible\&.  In particular, it is a good idea to
+put code that does not need to be run for every single shell behind
+a test of the form `\fBif [[ \-o rcs ]]; then \&.\&.\&.\fP' so that it will not
+be executed when zsh is invoked with the `\fB\-f\fP' option\&.
+.PP
+Any of these files may be pre\-compiled with the \fBzcompile\fP builtin
+command (see \fIzshbuiltins\fP(1))\&.  If a compiled file exists (named for the original file plus the
+\fB\&.zwc\fP extension) and it is newer than the original file, the compiled
+file will be used instead\&.
+.\" Yodl file: Zsh/filelist.yo
+.SH "FILES"
+.PD 0
+.TP
+\fB$ZDOTDIR/\&.zshenv\fP
+.TP
+\fB$ZDOTDIR/\&.zprofile\fP
+.TP
+\fB$ZDOTDIR/\&.zshrc\fP
+.TP
+\fB$ZDOTDIR/\&.zlogin\fP
+.TP
+\fB$ZDOTDIR/\&.zlogout\fP
+.TP
+\fB${TMPPREFIX}*\fP   (default is /tmp/zsh*)
+.TP
+\fB/etc/zshenv\fP
+.TP
+\fB/etc/zprofile\fP
+.TP
+\fB/etc/zshrc\fP
+.TP
+\fB/etc/zlogin\fP
+.TP
+\fB/etc/zlogout\fP    (installation\-specific \- \fB/etc\fP is the default)
+.PD
+.\" Yodl file: Zsh/seealso.yo
+.SH "SEE ALSO"
+\fIsh\fP(1),
+\fIcsh\fP(1),
+\fItcsh\fP(1),
+\fIrc\fP(1),
+\fIbash\fP(1),
+\fIksh\fP(1),
+\fIzshbuiltins\fP(1),
+\fIzshcompwid\fP(1),
+\fIzshcompsys\fP(1),
+\fIzshcompctl\fP(1),
+\fIzshexpn\fP(1),
+\fIzshmisc\fP(1),
+\fIzshmodules\fP(1),
+\fIzshoptions\fP(1),
+\fIzshparam\fP(1),
+\fIzshzle\fP(1)
+.PP
+\fBIEEE Standard for information Technology \-
+Portable Operating System Interface (POSIX) \-
+Part 2: Shell and Utilities\fP,
+IEEE Inc, 1993, ISBN 1\-55937\-255\-9\&.
--- zsh-beta-4.3.0-dev-1+20050424.orig/Doc/zshbuiltins.1
+++ zsh-beta-4.3.0-dev-1+20050424/Doc/zshbuiltins.1
@@ -0,0 +1,2042 @@
+.TH "ZSHBUILTINS" "1" "August 16, 2004" "zsh 4\&.2\&.1-dev-1"
+.SH "NAME"
+zshbuiltins \- zsh built\-in commands
+.\" Yodl file: Zsh/builtins.yo
+.SH "SHELL BUILTIN COMMANDS"
+.PD 0
+.TP
+.PD
+\fB\-\fP \fIsimple command\fP
+See the section `Precommand Modifiers'\&.
+.TP
+\fB\&.\fP \fIfile\fP [ \fIarg\fP \&.\&.\&. ]
+Read commands from \fIfile\fP and execute them in the current shell
+environment\&.
+.RS
+.PP
+If \fIfile\fP does not contain a slash, or if \fBPATH_DIRS\fP is set,
+the shell looks in the components of \fB$path\fP to find the directory
+containing \fIfile\fP\&.  Files in the current directory are not read
+unless `\fB\&.\fP' appears somewhere in \fB$path\fP\&.  If a file named
+`\fIfile\fP\fB\&.zwc\fP' is found, is newer than \fIfile\fP, and is the
+compiled form (created with the \fBzcompile\fP builtin) of \fIfile\fP,
+then commands are read from that file instead of \fIfile\fP\&.
+.PP
+If any arguments \fIarg\fP are given,
+they become the positional parameters; the old positional
+parameters are restored when the \fIfile\fP is done executing\&.
+The exit status is the exit status of the last command executed\&.
+.RE
+.TP
+\fB:\fP [ \fIarg\fP \&.\&.\&. ]
+This command does nothing, although normal argument expansions is performed
+which may have effects on shell parameters\&.  A zero exit code is returned\&.
+.TP
+\fBalias\fP [ {\fB+|\fB\-\fP\fP}\fBgmrsL\fP ] [ \fIname\fP[\fB=\fP\fIvalue\fP] \&.\&.\&. ]
+For each \fIname\fP with a corresponding \fIvalue\fP, define an alias
+with that value\&.  A trailing space in \fIvalue\fP causes the next word
+to be checked for alias expansion\&.  If the \fB\-g\fP flag is present,
+define a global alias; global aliases are expanded even if they do not
+occur in command position\&.
+.RS
+.PP
+If the \fB\-s\fP flags is present, define a suffix alias: if the command
+word on a command line is in the form `\fItext\fP\fB\&.\fP\fIname\fP', where
+\fItext\fP is any non\-empty string, it is replaced by the text
+`\fIvalue\fP \fItext\fP\fB\&.\fP\fIname\fP'\&.  Note that \fIname\fP is treated as
+a literal string, not a pattern\&.  A trailing space in \fIvalue\fP is not
+special in this case\&.  For example,
+.PP
+.RS
+.nf
+\fBalias \-s ps=gv\fP
+.fi
+.RE
+.PP
+will cause the command `\fB*\&.ps\fP' to be expanded to `\fBgv *\&.ps\fP'\&.  As
+alias expansion is carried out earlier than globbing, the `\fB*\&.ps\fP' will
+then be expanded\&.  Suffix aliases constitute a different name space from
+other aliases (so in the above example it is still possible
+to create an alias for the command \fBps\fP) and the two sets are never
+listed together\&.
+.PP
+For each \fIname\fP with no \fIvalue\fP,
+print the value of \fIname\fP, if any\&.  With no arguments, print all
+currently defined aliases other than suffix aliases\&.  If the \fB\-m\fP flag
+is given the arguments are taken as patterns (they should be quoted to
+preserve them from being interpreted as glob patterns), and the aliases
+matching these patterns are printed\&.  When printing aliases and one of
+the \fB\-g\fP, \fB\-r\fP or \fB\-s\fP flags is present, restrict the printing to
+global, regular or suffix aliases, respectively; a regular alias is one
+which is neither a global nor a suffix alias\&.   Using `\fB+\fP'
+instead of `\fB\-\fP', or ending the option list with a single
+`\fB+\fP', prevents the values of the aliases from being printed\&.
+.PP
+If the \fB\-L\fP flag is present, then print each
+alias in a manner suitable for putting in a startup script\&.  The exit
+status is nonzero if a \fIname\fP (with no \fIvalue\fP) is given for
+which no alias has been defined\&.
+.RE
+.TP
+\fBautoload\fP [ {\fB+\fP|\fB\-\fP}\fBUXktz\fP ] [ \fB\-w\fP ] [ \fIname\fP \&.\&.\&. ]
+Equivalent to \fBfunctions \-u\fP, with the exception of \fB\-X\fP/\fB+X\fP and
+\fB\-w\fP\&.
+.RS
+.PP
+The flag \fB\-X\fP may be used only inside a shell function, and may not be
+followed by a \fIname\fP\&.  It causes the calling function to be marked for
+autoloading and then immediately loaded and executed, with the current
+array of positional parameters as arguments\&.  This replaces the previous
+definition of the function\&.  If no function definition is found, an error
+is printed and the function remains undefined and marked for autoloading\&.
+.PP
+The flag \fB+X\fP attempts to load each \fIname\fP as an autoloaded function,
+but does \fInot\fP execute it\&.  The exit status is zero (success) if the
+function was not previously defined \fIand\fP a definition for it was found\&.
+This does \fInot\fP replace any existing definition of the function\&.  The
+exit status is nonzero (failure) if the function was already defined or
+when no definition was found\&.  In the latter case the function remains
+undefined and marked for autoloading\&.  If ksh\-style autoloading is
+enabled, the function created will contain the contents of the file
+plus a call to the function itself appended to it, thus giving normal
+ksh autoloading behaviour on the first call to the function\&.
+.PP
+With the \fB\-w\fP flag, the \fIname\fPs are taken as names of files compiled
+with the \fBzcompile\fP builtin, and all functions defined in them are
+marked for autoloading\&.
+.RE
+.TP
+.PD 0
+\fBbg\fP [ \fIjob\fP \&.\&.\&. ]
+.TP
+.PD
+\fIjob\fP \&.\&.\&. \fB&\fP
+Put each specified \fIjob\fP in the background,
+or the current job if none is specified\&.
+.TP
+\fBbindkey\fP
+See the section `Zle Builtins' in \fIzshzle\fP(1)\&.
+.TP
+\fBbreak\fP [ \fIn\fP ]
+Exit from an enclosing \fBfor\fP, \fBwhile\fP,
+\fBuntil\fP, \fBselect\fP or \fBrepeat\fP loop\&.  If \fIn\fP
+is specified, then break \fIn\fP levels instead of just one\&.
+.TP
+\fBbuiltin\fP \fIname\fP [ \fIargs\fP \&.\&.\&. ]
+Executes the builtin \fIname\fP, with the given \fIargs\fP\&.
+.TP
+\fBbye\fP
+Same as \fBexit\fP\&.
+.TP
+\fBcap\fP
+See the section `The zsh/cap Module' in \fIzshmodules\fP(1)\&.
+.TP
+.PD 0
+\fBcd\fP [ \fB\-sLP\fP ] [ \fIarg\fP ]
+.TP
+.PD 0
+\fBcd\fP [ \fB\-sLP\fP ] \fIold\fP \fInew\fP
+.TP
+.PD
+\fBcd\fP [ \fB\-sLP\fP ] {\fB+\fP|\fB\-\fP}\fIn\fP
+Change the current directory\&.  In the first form, change the
+current directory to \fIarg\fP, or to the value of \fB$HOME\fP if
+\fIarg\fP is not specified\&.  If \fIarg\fP is `\fB\-\fP', change to the
+value of \fB$OLDPWD\fP, the previous directory\&.
+Otherwise, if a directory named \fIarg\fP is not found in the current
+directory and \fIarg\fP does not begin with a slash, search each
+component of the shell parameter \fBcdpath\fP\&.  If no directory is found
+and the option \fBCDABLE_VARS\fP is set, and a parameter named \fIarg\fP
+exists whose value begins with a slash, treat its value as the
+directory\&.  In that case, the parameter is added to the named
+directory hash table\&.
+.RS
+.PP
+The second form of \fBcd\fP substitutes the string \fInew\fP
+for the string \fIold\fP in the name of the current directory,
+and tries to change to this new directory\&.
+.PP
+The third form of \fBcd\fP extracts an entry from the directory
+stack, and changes to that directory\&.  An argument of the form
+`\fB+\fP\fIn\fP' identifies a stack entry by counting from the left
+of the list shown by the \fBdirs\fP command, starting with zero\&.
+An argument of the form `\fB\-\fP\fIn\fP' counts from the right\&.
+If the \fBPUSHD_MINUS\fP option is set, the meanings of `\fB+\fP'
+and `\fB\-\fP' in this context are swapped\&.
+.PP
+If the \fB\-s\fP option is specified, \fBcd\fP refuses to change the current
+directory if the given pathname contains symlinks\&.  If the \fB\-P\fP option
+is given or the \fBCHASE_LINKS\fP option is set, symbolic links are resolved
+to their true values\&.  If the \fB\-L\fP option is given symbolic links are
+followed regardless of the state of the \fBCHASE_LINKS\fP option\&.
+.RE
+.TP
+\fBchdir\fP
+Same as \fBcd\fP\&.
+.TP
+\fBclone\fP
+See the section `The zsh/clone Module' in \fIzshmodules\fP(1)\&.
+.TP
+\fBcommand\fP [ \fB\-pvV\fP ] \fIsimple command\fP
+The simple command argument is taken as an external command instead of
+a function or builtin and is executed\&. If the \fBPOSIX_BUILTINS\fP option
+is set, builtins will also be executed but certain special properties
+of them are suppressed\&. The \fB\-p\fP flag causes a default path to be
+searched instead of that in \fB$path\fP\&. With the \fB\-v\fP flag, \fBcommand\fP
+is similar to \fBwhence\fP and with \fB\-V\fP, it is equivalent to \fBwhence
+\-v\fP\&.
+.RS
+.PP
+See also the section `Precommand Modifiers'\&.
+.RE
+.TP
+\fBcomparguments\fP
+See the section `The zsh/computil Module' in \fIzshmodules\fP(1)\&.
+.TP
+\fBcompcall\fP
+See the section `The zsh/compctl Module' in \fIzshmodules\fP(1)\&.
+.TP
+\fBcompctl\fP
+See the section `The zsh/compctl Module' in \fIzshmodules\fP(1)\&.
+.TP
+\fBcompdescribe\fP
+See the section `The zsh/computil Module' in \fIzshmodules\fP(1)\&.
+.TP
+\fBcompfiles\fP
+See the section `The zsh/computil Module' in \fIzshmodules\fP(1)\&.
+.TP
+\fBcompgroups\fP
+See the section `The zsh/computil Module' in \fIzshmodules\fP(1)\&.
+.TP
+\fBcompquote\fP
+See the section `The zsh/computil Module' in \fIzshmodules\fP(1)\&.
+.TP
+\fBcomptags\fP
+See the section `The zsh/computil Module' in \fIzshmodules\fP(1)\&.
+.TP
+\fBcomptry\fP
+See the section `The zsh/computil Module' in \fIzshmodules\fP(1)\&.
+.TP
+\fBcompvalues\fP
+See the section `The zsh/computil Module' in \fIzshmodules\fP(1)\&.
+.TP
+\fBcontinue\fP [ \fIn\fP ]
+Resume the next iteration of the enclosing
+\fBfor\fP, \fBwhile\fP, \fBuntil\fP, \fBselect\fP or
+\fBrepeat\fP loop\&.  If \fIn\fP is specified, break out of
+\fIn\fP\-1 loops and resume at the \fIn\fPth enclosing loop\&.
+.TP
+\fBdeclare\fP
+Same as \fBtypeset\fP\&.
+.TP
+.PD 0
+\fBdirs\fP [ \fB\-c\fP ] [ \fIarg\fP \&.\&.\&. ]
+.TP
+.PD
+\fBdirs\fP [ \fB\-lpv\fP ]
+With no arguments, print the contents of the directory stack\&.
+Directories are added to this stack with the \fBpushd\fP command,
+and removed with the \fBcd\fP or \fBpopd\fP commands\&.
+If arguments are specified, load them onto the directory stack,
+replacing anything that was there, and push the current directory
+onto the stack\&.
+.RS
+.PP
+.PD 0
+.TP
+.PD
+\fB\-c\fP
+clear the directory stack\&.
+.TP
+\fB\-l\fP
+print directory names in full instead of using of using \fB~\fP expressions\&.
+.TP
+\fB\-p\fP
+print directory entries one per line\&.
+.TP
+\fB\-v\fP
+number the directories in the stack when printing\&.
+.PP
+.RE
+.TP
+\fBdisable\fP [ \fB\-afmrs\fP ] \fIname\fP \&.\&.\&.
+Temporarily disable the \fIname\fPd hash table elements\&.  The default
+is to disable builtin commands\&.  This allows you to use an external
+command with the same name as a builtin command\&.  The \fB\-a\fP option
+causes \fBdisable\fP to act on regular or global aliases\&.  The \fB\-s\fP
+option causes \fBdisable\fP to act on suffix aliases\&.  The \fB\-f\fP option causes
+\fBdisable\fP to act on shell functions\&.  The \fB\-r\fP options causes
+\fBdisable\fP to act on reserved words\&.  Without arguments all disabled
+hash table elements from the corresponding hash table are printed\&.
+With the \fB\-m\fP flag the arguments are taken as patterns (which should be
+quoted to prevent them from undergoing filename expansion), and all hash
+table elements from the corresponding hash table matching these patterns
+are disabled\&.  Disabled objects can be enabled with the \fBenable\fP
+command\&.
+.TP
+.PD 0
+\fBdisown\fP [ \fIjob\fP \&.\&.\&. ]
+.TP
+.PD 0
+\fIjob\fP \&.\&.\&. \fB&|\fP
+.TP
+.PD
+\fIjob\fP \&.\&.\&. \fB&!\fP
+Remove the specified \fIjob\fPs from the job table; the shell will
+no longer report their status, and will not complain if you
+try to exit an interactive shell with them running or stopped\&.
+If no \fIjob\fP is specified, disown the current job\&.
+.RS
+.PP
+If the \fIjob\fPs are currently stopped and the \fBAUTO_CONTINUE\fP option
+is not set, a warning is printed containing information about how to
+make them running after they have been disowned\&.  If one of the latter
+two forms is used, the \fIjob\fPs will automatically be made running,
+independent of the setting of the \fBAUTO_CONTINUE\fP option\&.
+.RE
+.TP
+\fBecho\fP [ \fB\-neE\fP ] [ \fIarg\fP \&.\&.\&. ]
+Write each \fIarg\fP on the standard output, with a space separating
+each one\&.
+If the \fB\-n\fP flag is not present, print a newline at the end\&.
+\fBecho\fP recognizes the following escape sequences:
+.RS
+.PP
+.PD 0
+.TP
+\fB\ea\fP
+bell character
+.TP
+\fB\eb\fP
+backspace
+.TP
+\fB\ec\fP
+suppress final newline
+.TP
+\fB\ee\fP
+escape
+.TP
+\fB\ef\fP
+form feed
+.TP
+\fB\en\fP
+linefeed (newline)
+.TP
+\fB\er\fP
+carriage return
+.TP
+\fB\et\fP
+horizontal tab
+.TP
+\fB\ev\fP
+vertical tab
+.TP
+\fB\e\e\fP
+backslash
+.TP
+\fB\e0\fP\fINNN\fP
+character code in octal
+.TP
+\fB\ex\fP\fINN\fP
+character code in hexadecimal
+.TP
+\fB\eu\fP\fINNNN\fP
+unicode character code in hexadecimal
+.TP
+\fB\eU\fP\fINNNNNNNN\fP
+unicode character code in hexadecimal
+.PD
+.PP
+The \fB\-E\fP flag, or the \fBBSD_ECHO\fP option, can be used to disable
+these escape sequences\&.  In the latter case, \fB\-e\fP flag can be used to
+enable them\&.
+.RE
+.TP
+\fBechotc\fP
+See the section `The zsh/termcap Module' in \fIzshmodules\fP(1)\&.
+.TP
+\fBechoti\fP
+See the section `The zsh/terminfo Module' in \fIzshmodules\fP(1)\&.
+.TP
+\fBemulate\fP [ \fB\-LR\fP ] {\fBzsh\fP|\fBsh\fP|\fBksh\fP|\fBcsh\fP}
+Set up zsh options to emulate the specified shell as much as possible\&.
+\fBcsh\fP will never be fully emulated\&.
+If the argument is not one of the shells listed above, \fBzsh\fP
+will be used as a default; more precisely, the tests performed on the
+argument are the same as those used to determine the emulation at startup
+based on the shell name, see
+the section `Compatibility' in \fIzshmisc\fP(1)
+\&.  If the \fB\-R\fP option is given, all options
+are reset to their default value corresponding to the specified emulation
+mode, except for certain options describing the interactive
+environment; otherwise, only those options likely to cause portability
+problems in scripts and functions are altered\&.  If the \fB\-L\fP option
+is given, the options \fBLOCAL_OPTIONS\fP and \fBLOCAL_TRAPS\fP will be set as
+well, causing the effects of the \fBemulate\fP command and any \fBsetopt\fP and
+\fBtrap\fP commands to be local to the immediately surrounding shell
+function, if any; normally these options are turned off in all emulation
+modes except \fBksh\fP\&.
+.TP
+\fBenable\fP [ \fB\-afmrs\fP ] \fIname\fP \&.\&.\&.
+Enable the \fIname\fPd hash table elements, presumably disabled
+earlier with \fBdisable\fP\&.  The default is to enable builtin commands\&.
+The \fB\-a\fP option causes \fBenable\fP to act on regular or global aliases\&.
+The \fB\-s\fP option causes \fBenable\fP to act on suffix aliases\&.
+The \fB\-f\fP option causes \fBenable\fP to act on shell functions\&.  The \fB\-r\fP
+option causes \fBenable\fP to act on reserved words\&.  Without arguments
+all enabled hash table elements from the corresponding hash table are
+printed\&.  With the \fB\-m\fP flag the arguments are taken as patterns
+(should be quoted) and all hash table elements from the corresponding
+hash table matching these patterns are enabled\&.  Enabled objects can be
+disabled with the \fBdisable\fP builtin command\&.
+.TP
+\fBeval\fP [ \fIarg\fP \&.\&.\&. ]
+Read the arguments as input to the shell and execute the resulting
+command in the current shell process\&.
+.TP
+\fBexec\fP \fIsimple command\fP
+See the section `Precommand Modifiers'\&.
+.TP
+\fBexit\fP [ \fIn\fP ]
+Exit the shell with the exit code specified by \fIn\fP; if none
+is specified, use the exit code from the last command executed\&.
+An EOF condition will also cause the shell to exit, unless
+the \fBIGNORE_EOF\fP option is set\&.
+.TP
+\fBexport\fP [ \fIname\fP[\fB=\fP\fIvalue\fP] \&.\&.\&. ]
+The specified \fIname\fPs are marked for automatic export
+to the environment of subsequently executed commands\&.
+Equivalent to \fBtypeset \-gx\fP\&.
+If a parameter specified does not
+already exist, it is created in the global scope\&.
+.TP
+\fBfalse\fP [ \fIarg\fP \&.\&.\&. ]
+Do nothing and return an exit code of 1\&.
+.TP
+.PD 0
+\fBfc\fP [ \fB\-e\fP \fIename\fP ] [ \fB\-nlrdDfEim\fP ] [ \fIold\fP\fB=\fP\fInew\fP \&.\&.\&. ] [ \fIfirst\fP [ \fIlast\fP ] ]
+.TP
+.PD 0
+\fBfc\fP \fB\-p\fP [ \fB\-a\fP ] [ \fIfilename\fP [ \fIhistsize\fP [ \fIsavehistsize\fP ] ] ]
+.TP
+.PD 0
+\fBfc\fP \fB\-P\fP
+.TP
+.PD
+\fBfc\fP \fB\-ARWI\fP [ \fIfilename\fP ]
+Select a range of commands from \fIfirst\fP to \fIlast\fP from the
+history list\&.
+The arguments \fIfirst\fP and \fIlast\fP may be specified as a
+number or as a string\&.  A negative number is used as an offset
+to the current history event number\&.
+A string specifies the most recent event beginning with the given string\&.
+All substitutions \fIold\fP\fB=\fP\fInew\fP, if any, are then performed
+on the commands\&.
+.RS
+.PP
+If the \fB\-l\fP flag is given, the resulting commands are listed on
+standard output\&.
+If the \fB\-m\fP flag is also given the first argument is taken as a
+pattern (should be quoted) and only the history events matching this
+pattern will be shown\&.
+Otherwise the editor program \fIename\fP is invoked on a file containing
+these history events\&.  If \fIename\fP is not given, the value
+of the parameter \fBFCEDIT\fP is used\&.  If \fIename\fP is `\fB\-\fP',
+no editor is invoked\&.  When editing is complete, the edited
+command is executed\&.
+.PP
+If \fIfirst\fP is not specified, it will be set to \-1 (the most recent
+event), or to \-16 if the \fB\-l\fP flag is given\&.
+If \fIlast\fP is not specified, it will be set to \fIfirst\fP,
+or to \-1 if the \fB\-l\fP flag is given\&.
+.PP
+The flag \fB\-r\fP reverses the order of the commands and the
+flag \fB\-n\fP suppresses command numbers when listing\&.
+Also when listing, \fB\-d\fP prints timestamps for each command, and
+\fB\-f\fP prints full time\-date stamps\&.  Adding the \fB\-E\fP flag
+causes the dates to be printed as `\fIdd\fP\fB\&.\fP\fImm\fP\fB\&.\fP\fIyyyy\fP',
+instead of the default `\fImm\fP\fB/\fP\fIdd\fP\fB/\fP\fIyyyy\fP'\&.
+Adding the \fB\-i\fP flag causes the dates to be printed in ISO8601
+`\fIyyyy\fP\fB\-\fP\fImm\fP\fB\-\fP\fIdd\fP' format\&.
+With the \fB\-D\fP flag, \fBfc\fP prints elapsed times\&.
+.PP
+.PP
+`\fBfc \-p\fP' pushes the current history list onto a stack and switches to a
+new history list\&.  If the \fB\-a\fP option is also specified, this history list
+will be automatically popped when the current function scope is exited, which
+is a much better solution than creating a trap function to call `\fBfc \-P\fP'
+manually\&.  If no arguments are specified, the history list is left empty,
+\fB$HISTFILE\fP is unset, and \fB$HISTSIZE\fP & \fB$SAVEHIST\fP are set to their
+default values\&.  If one argument is given, \fB$HISTFILE\fP is set to that
+filename, \fB$HISTSIZE\fP & \fB$SAVEHIST\fP are left unchanged, and the history
+file is read in (if it exists) to initialize the new list\&.  If a second
+argument is specified, \fB$HISTSIZE\fP & \fB$SAVEHIST\fP are instead set to the
+single specified numeric value\&.  Finally, if a third argument is specified,
+\fB$SAVEHIST\fP is set to a separate value from \fB$HISTSIZE\fP\&.  You are free to
+change these environment values for the new history list however you desire
+in order to manipulate the new history list\&.
+.PP
+`\fBfc \-P\fP' pops the history list back to an older list saved by `\fBfc \-p\fP'\&.
+The current list is saved to its \fB$HISTFILE\fP before it is destroyed
+(assuming that \fB$HISTFILE\fP and \fB$SAVEHIST\fP are set appropriately, of
+course)\&.  The values of \fB$HISTFILE\fP, \fB$HISTSIZE\fP, and \fB$SAVEHIST\fP are
+restored to the values they had when `\fBfc \-p\fP' was called\&.  Note that this
+restoration can conflict with making these variables "local", so your best
+bet is to avoid local declarations for these variables in functions that use
+`\fBfc \-p\fP'\&.  The one other guaranteed\-safe combination is declaring these
+variables to be local at the top of your function and using the automatic
+option (\fB\-a\fP) with `\fBfc \-p\fP'\&.  Finally, note that it is legal to manually
+pop a push marked for automatic popping if you need to do so before the
+function exits\&.
+.PP
+`\fBfc \-R\fP' reads the history from the given file,
+`\fBfc \-W\fP' writes the history out to the given file,
+and `\fBfc \-A\fP' appends the history out to the given file\&.
+If no filename is specified, the \fB$HISTFILE\fP is assumed\&.
+If the \fB\-I\fP option is added to \fB\-R\fP, only those events that are
+not already contained within the internal history list are added\&.
+If the \fB\-I\fP option is added to \fB\-A\fP or \fB\-W\fP, only those
+events that are new since last incremental append/write to
+the history file are appended/written\&.
+In any case, the created file will have no more than \fB$SAVEHIST\fP
+entries\&.
+.RE
+.TP
+.PD 0
+\fBfg\fP [ \fIjob\fP \&.\&.\&. ]
+.TP
+.PD
+\fIjob\fP \&.\&.\&.
+Bring each specified \fIjob\fP in turn to the foreground\&.
+If no \fIjob\fP is specified, resume the current job\&.
+.TP
+\fBfloat\fP [ {\fB+\fP|\fB\-\fP}\fBEFHghlprtux\fP ] [ \fIname\fP[\fB=\fP\fIvalue\fP] \&.\&.\&. ]
+Equivalent to \fBtypeset \-E\fP, except that options irrelevant to floating
+point numbers are not permitted\&.
+.TP
+\fBfunctions\fP [ {\fB+\fP|\fB\-\fP}\fBUXkmtuz\fP ] [ \fIname\fP \&.\&.\&. ]
+Equivalent to \fBtypeset \-f\fP\&.
+.TP
+\fBgetcap\fP
+See the section `The zsh/cap Module' in \fIzshmodules\fP(1)\&.
+.TP
+\fBgetln\fP [ \fB\-AclneE\fP ] \fIname\fP \&.\&.\&.
+Read the top value from the buffer stack and put it in
+the shell parameter \fBname\fP\&.  Equivalent to
+\fBread \-zr\fP\&.
+.TP
+\fBgetopts\fP \fIoptstring\fP \fIname\fP [ \fIarg\fP \&.\&.\&. ]
+Checks the \fIarg\fPs for legal options\&.  If the \fIarg\fPs are omitted,
+use the positional parameters\&.  A valid option argument
+begins with a `\fB+\fP' or a `\fB\-\fP'\&.  An argument not beginning with
+a `\fB+\fP' or a `\fB\-\fP', or the argument `\fB\-\-\fP', ends the options\&.
+Note that a single `\fB\-\fP' is not considered a valid option argument\&.
+\fIoptstring\fP contains the letters that \fBgetopts\fP
+recognizes\&.  If a letter is followed by a `\fB:\fP', that option
+is expected to have an argument\&.  The options can be
+separated from the argument by blanks\&.
+.RS
+.PP
+Each time it is invoked, \fBgetopts\fP places the option letter it finds
+in the shell parameter \fIname\fP, prepended with a `\fB+\fP' when
+\fIarg\fP begins with a `\fB+\fP'\&.  The index of the next \fIarg\fP
+is stored in \fBOPTIND\fP\&.  The option argument, if any,
+is stored in \fBOPTARG\fP\&.
+.PP
+The first option to be examined may be changed by explicitly assigning
+to \fBOPTIND\fP\&.  \fBOPTIND\fP has an initial value of \fB1\fP, and is
+normally reset to \fB1\fP upon exit from a shell function\&.  \fBOPTARG\fP
+is not reset and retains its value from the most recent call to
+\fBgetopts\fP\&.  If either of \fBOPTIND\fP or \fBOPTARG\fP is explicitly
+unset, it remains unset, and the index or option argument is not
+stored\&.  The option itself is still stored in \fIname\fP in this case\&.
+.PP
+A leading `\fB:\fP' in \fIoptstring\fP causes \fBgetopts\fP to store the
+letter of any invalid option in \fBOPTARG\fP, and to set \fIname\fP to
+`\fB?\fP' for an unknown option and to `\fB:\fP' when a required option is
+missing\&.  Otherwise, \fBgetopts\fP sets \fIname\fP to `\fB?\fP' and prints
+an error message when an option is invalid\&.  The exit status is
+nonzero when there are no more options\&.
+.RE
+.TP
+\fBhash\fP [ \fB\-Ldfmrv\fP ] [ \fIname\fP[\fB=\fP\fIvalue\fP] ] \&.\&.\&.
+\fBhash\fP can be used to directly modify the contents of the command
+hash table, and the named directory hash table\&.  Normally one would
+modify these tables by modifying one's \fBPATH\fP
+(for the command hash table) or by creating appropriate shell parameters
+(for the named directory hash table)\&.
+The choice of hash table to work on is determined by the \fB\-d\fP option;
+without the option the command hash table is used, and with the option the
+named directory hash table is used\&.
+.RS
+.PP
+Given no arguments, and neither the \fB\-r\fP or \fB\-f\fP options,
+the selected hash table will be listed in full\&.
+.PP
+The \fB\-r\fP option causes the selected hash table to be emptied\&.
+It will be subsequently rebuilt in the normal fashion\&.
+The \fB\-f\fP option causes the selected hash table to be fully
+rebuilt immediately\&.  For the command hash table this hashes
+all the absolute directories in the \fBPATH\fP,
+and for the named directory hash table this adds all users' home directories\&.
+These two options cannot be used with any arguments\&.
+.PP
+The \fB\-m\fP option causes the arguments to be taken as patterns
+(which should be quoted) and the elements of the hash table
+matching those patterns are printed\&.  This is the only way to display
+a limited selection of hash table elements\&.
+.PP
+For each \fIname\fP with a corresponding \fIvalue\fP, put `\fIname\fP' in
+the selected hash table, associating it with the pathname `\fIvalue\fP'\&.
+In the command hash table, this means that
+whenever `\fIname\fP' is used as a command argument, the shell will try
+to execute the file given by `\fIvalue\fP'\&.
+In the named directory hash table, this means
+that `\fIvalue\fP' may be referred to as `\fB~\fP\fIname\fP'\&.
+.PP
+For each \fIname\fP with no
+corresponding \fIvalue\fP, attempt to add \fIname\fP to the hash table,
+checking what the appropriate \fBvalue\fP is in the normal manner for
+that hash table\&.  If an appropriate \fBvalue\fP can't be found, then
+the hash table will be unchanged\&.
+.PP
+The \fB\-v\fP option causes hash table entries to be listed as they are
+added by explicit specification\&.  If has no effect if used with \fB\-f\fP\&.
+.PP
+If the \fB\-L\fP flag is present, then each hash table entry is printed in
+the form of a call to hash\&.
+.RE
+.TP
+\fBhistory\fP
+Same as \fBfc \-l\fP\&.
+.TP
+\fBinteger\fP [ {\fB+\fP|\fB\-\fP}\fBHghilprtux\fP ] [ \fIname\fP[\fB=\fP\fIvalue\fP] \&.\&.\&. ]
+Equivalent to \fBtypeset \-i\fP, except that options irrelevant to
+integers are not permitted\&.
+.TP
+.PD 0
+\fBjobs\fP [ \fB\-dlprs\fP ] [ \fIjob\fP \&.\&.\&. ]
+.TP
+.PD
+\fBjobs \-Z\fP \fIstring\fP
+Lists information about each given job, or all jobs
+if \fIjob\fP is omitted\&.  The \fB\-l\fP flag lists process
+IDs, and the \fB\-p\fP flag lists process groups\&.
+If the \fB\-r\fP flag is specified only running jobs will be listed
+and if the \fB\-s\fP flag is given only stopped jobs are shown\&.
+If the \fB\-d\fP flag is given, the directory from which the job was
+started (which may not be the current directory of the job) will also
+be shown\&.
+.RS
+.PP
+The \fB\-Z\fP option replaces the shell's argument and environment space with
+the given string, truncated if necessary to fit\&.  This will normally be
+visible in \fBps\fP (\fIps\fP(1)) listings\&.  This feature is typically
+used by daemons, to indicate their state\&.
+.RE
+.TP
+.PD 0
+\fBkill\fP [ \fB\-s\fP \fIsignal_name\fP | \fB\-n\fP \fIsignal_number\fP | \fB\-\fP\fIsig\fP ] \fIjob\fP \&.\&.\&.
+.TP
+.PD
+\fBkill\fP \fB\-l\fP [ \fIsig\fP \&.\&.\&. ]
+Sends either \fBSIGTERM\fP or the specified signal to the given
+jobs or processes\&.
+Signals are given by number or by names, with or without the `\fBSIG\fP'
+prefix\&.
+If the signal being sent is not `\fBKILL\fP' or `\fBCONT\fP', then the job
+will be sent a `\fBCONT\fP' signal if it is stopped\&.
+The argument \fIjob\fP can be the process ID of a job
+not in the job list\&.
+In the second form, \fBkill \-l\fP, if \fIsig\fP is not
+specified the signal names are listed\&.  Otherwise, for each
+\fIsig\fP that is a name, the corresponding signal number is
+listed\&.  For each \fIsig\fP that is a signal number or a number
+representing the exit status of a process which was terminated or
+stopped by a signal the name of the signal is printed\&.
+.TP
+\fBlet\fP \fIarg\fP \&.\&.\&.
+Evaluate each \fIarg\fP as an arithmetic expression\&.
+See the section `Arithmetic Evaluation' for a description
+of arithmetic expressions\&.  The exit status is 0 if the
+value of the last expression is nonzero, and 1 otherwise\&.
+.TP
+\fBlimit\fP [ \fB\-hs\fP ] [ \fIresource\fP [ \fIlimit\fP ] ] \&.\&.\&.
+Set or display resource limits\&.  Unless the \fB\-s\fP flag is given,
+the limit applies only the children of the shell\&.  If \fB\-s\fP is
+given without other arguments, the resource limits of the current
+shell is set to the previously set resource limits of the children\&.
+.RS
+.PP
+If \fIlimit\fP is not specified, print the current limit placed
+on \fIresource\fP, otherwise
+set the limit to the specified value\&.  If the \fB\-h\fP flag
+is given, use hard limits instead of soft limits\&.
+If no \fIresource\fP is given, print all limits\&.
+.PP
+When looping over multiple resources, the shell will abort immediately if
+it detects a badly formed argument\&.  However, if it fails to set a limit
+for some other reason it will continue trying to set the remaining limits\&.
+.PP
+\fIresource\fP can be one of:
+.PP
+.PD 0
+.TP
+\fBaddressspace\fP
+Maximum amount of address space used\&.
+.TP
+\fBaiomemorylocked\fP
+Maximum amount of memory locked in RAM for AIO operations\&.
+.TP
+\fBaiooperations\fP
+Maximum number of AIO operations\&.
+.TP
+\fBcachedthreads\fP
+Maximum number of cached threads\&.
+.TP
+\fBcoredumpsize\fP
+Maximum size of a core dump\&.
+.TP
+\fBcputime\fP
+Maximum CPU seconds per process\&.
+.TP
+\fBdatasize\fP
+Maximum data size (including stack) for each process\&.
+.TP
+\fBdescriptors\fP
+Maximum value for a file descriptor\&.
+.TP
+\fBfilesize\fP
+Largest single file allowed\&.
+.TP
+\fBmaxproc\fP
+Maximum number of processes\&.
+.TP
+\fBmaxpthreads\fP
+Maximum number of threads per process\&.
+.TP
+\fBmemorylocked\fP
+Maximum amount of memory locked in RAM\&.
+.TP
+\fBmemoryuse\fP
+Maximum resident set size\&.
+.TP
+\fBresident\fP
+Maximum resident set size\&.
+.TP
+\fBsockbufsize\fP
+Maximum size of all socket buffers\&.
+.TP
+\fBstacksize\fP
+Maximum stack size for each process\&.
+.TP
+\fBvmemorysize\fP
+Maximum amount of virtual memory\&.
+.PD
+.PP
+Which of these resource limits are available depends on the system\&.
+\fIresource\fP can be abbreviated to any unambiguous prefix\&.  It
+can also be an integer, which corresponds to the integer defined
+for the resource by the operating system\&.
+.PP
+If argument corresponds to a number which is out of the range of the
+resources configured into the shell, the shell will try to read or write
+the limit anyway, and will report an error if this fails\&.  As the shell
+does not store such resources internally, an attempt to set the limit will
+fail unless the \fB\-s\fP option is present\&.
+.PP
+\fIlimit\fP is a number, with an optional scaling factor, as follows:
+.PP
+.PD 0
+.TP
+\fIn\fP\fBh\fP
+hours
+.TP
+\fIn\fP\fBk\fP
+kilobytes (default)
+.TP
+\fIn\fP\fBm\fP
+megabytes or minutes
+.TP
+[\fImm\fP\fB:\fP]\fIss\fP
+minutes and seconds
+.PD
+.RE
+.TP
+\fBlocal\fP [ {\fB+\fP|\fB\-\fP}\fBAEFHLRUZahilprtux\fP [\fIn\fP]] [ \fIname\fP[\fB=\fP\fIvalue\fP] ] \&.\&.\&.
+Same as \fBtypeset\fP, except that the options \fB\-g\fP, and
+\fB\-f\fP are not permitted\&.  In this case the \fB\-x\fP option does not force
+the use of \fB\-g\fP, i\&.e\&. exported variables will be local to functions\&.
+.TP
+\fBlog\fP
+List all users currently logged in who are affected by
+the current setting of the \fBwatch\fP parameter\&.
+.TP
+\fBlogout\fP [ \fIn\fP ]
+Same as \fBexit\fP, except that it only works in a login shell\&.
+.TP
+\fBnoglob\fP \fIsimple command\fP
+See the section `Precommand Modifiers'\&.
+.TP
+\fBpopd\fP [ {\fB+\fP|\fB\-\fP}\fIn\fP ]
+Remove an entry from the directory stack, and perform a \fBcd\fP to
+the new top directory\&.  With no argument, the current top entry is
+removed\&.  An argument of the form `\fB+\fP\fIn\fP' identifies a stack
+entry by counting from the left of the list shown by the \fBdirs\fP command,
+starting with zero\&.  An argument of the form \fB\-n\fP counts from the right\&.
+If the \fBPUSHD_MINUS\fP option is set, the meanings of `\fB+\fP' and
+`\fB\-\fP' in this context are swapped\&.
+.TP
+.PD 0
+\fBprint\fP [ \fB\-abcDilmnNoOpPrsz\fP ] [ \fB\-u\fP \fIn\fP ] [ \fB\-f\fP \fIformat\fP ] [ \fB\-C\fP \fIcols\fP ]
+.TP
+.PD
+  [ \fB\-R\fP [ \fB\-en\fP ]] [ \fIarg\fP \&.\&.\&. ]
+With the `\fB\-f\fP' option the arguments are printed as described by \fBprintf\fP\&.
+With no flags or with the flag `\fB\-\fP', the arguments are printed on
+the standard output as described by \fBecho\fP, with the following differences:
+the escape sequence `\fB\eM\-\fP\fIx\fP' metafies the character
+\fIx\fP (sets the highest bit),
+`\fB\eC\-\fP\fIx\fP' produces a control character (`\fB\eC\-@\fP' and `\fB\eC\-?\fP' give the
+characters NUL and delete), and `\fB\eE\fP' is a synonym for `\fB\ee\fP'\&.
+Finally, if not in an escape
+sequence, `\fB\e\fP' escapes the following character and is not printed\&.
+.RS
+.PP
+.PD 0
+.TP
+.PD
+\fB\-a\fP
+Print arguments with the column incrementing first\&.  Only useful with the
+\fB\-c\fP and \fB\-C\fP options\&.
+.TP
+\fB\-b\fP
+Recognize all the escape sequences defined for the \fBbindkey\fP command,
+see 
+\fIzshzle\fP(1)\&.
+.TP
+\fB\-c\fP
+Print the arguments in columns\&.  Unless \fB\-a\fP is also given, arguments are
+printed with the row incrementing first\&.
+.TP
+\fB\-C\fP \fIcols\fP
+Print the arguments in \fIcols\fP columns\&.  Unless \fB\-a\fP is also given,
+arguments are printed with the row incrementing first\&.
+.TP
+\fB\-D\fP
+Treat the arguments as directory names, replacing prefixes with \fB~\fP
+expressions, as appropriate\&.
+.TP
+\fB\-i\fP
+If given together with \fB\-o\fP or \fB\-O\fP, sorting is performed
+case\-independently\&.
+.TP
+\fB\-l\fP
+Print the arguments separated by newlines instead of spaces\&.
+.TP
+\fB\-m\fP
+Take the first argument as a pattern (should be quoted), and remove
+it from the argument list together with subsequent arguments that
+do not match this pattern\&.
+.TP
+\fB\-n\fP
+Do not add a newline to the output\&.
+.TP
+\fB\-N\fP
+Print the arguments separated and terminated by nulls\&.
+.TP
+\fB\-o\fP
+Print the arguments sorted in ascending order\&.
+.TP
+\fB\-O\fP
+Print the arguments sorted in descending order\&.
+.TP
+\fB\-p\fP
+Print the arguments to the input of the coprocess\&.
+.TP
+\fB\-P\fP
+Perform prompt expansion (see
+\fIzshmisc\fP(1))\&.
+.TP
+\fB\-r\fP
+Ignore the escape conventions of \fBecho\fP\&.
+.TP
+\fB\-R\fP
+Emulate the BSD \fBecho\fP command, which does not process escape sequences
+unless the \fB\-e\fP flag is given\&.  The \fB\-n\fP flag suppresses the trailing
+newline\&.  Only the \fB\-e\fP and \fB\-n\fP flags are recognized after
+\fB\-R\fP; all other arguments and options are printed\&.
+.TP
+\fB\-s\fP
+Place the results in the history list instead of on the standard output\&.
+.TP
+\fB\-u\fP \fIn\fP
+Print the arguments to file descriptor \fIn\fP\&.
+.TP
+\fB\-z\fP
+Push the arguments onto the editing buffer stack, separated by spaces\&.
+.PP
+If any of `\fB\-m\fP', `\fB\-o\fP' or `\fB\-O\fP' are used in combination with
+`\fB\-f\fP' and there are no arguments (after the removal process in the
+case of `\fB\-m\fP') then nothing is printed\&.
+.RE
+.TP
+\fBprintf\fP \fIformat\fP [ \fIarg\fP \&.\&.\&. ]
+Print the arguments according to the format specification\&. Formatting
+rules are the same as used in C\&. The same escape sequences as for \fBecho\fP
+are recognised in the format\&. All C conversion specifications ending in
+one of csdiouxXeEfgGn are handled\&. In addition to this, `\fB%b\fP' can be
+used instead of `\fB%s\fP' to cause escape sequences in the argument to be
+recognised and `\fB%q\fP' can be used to quote the argument in such a way
+that allows it to be reused as shell input\&. With the numeric format
+specifiers, if the corresponding argument starts with a quote character,
+the numeric value of the following character is used as the number to
+print otherwise the argument is evaluated as an arithmetic expression\&. See
+the section `Arithmetic Evaluation' for a description of arithmetic
+expressions\&. With `\fB%n\fP', the corresponding argument is taken as an
+identifier which is created as an integer parameter\&.
+.RS
+.PP
+Normally, conversion specifications are applied to each argument in order
+but they can explicitly specify the \fIn\fPth argument is to be used by
+replacing `\fB%\fP' by `\fB%\fP\fIn\fP\fB$\fP' and `\fB*\fP' by `\fB*\fP\fIn\fP\fB$\fP'\&.
+It is recommended that you do not mix references of this explicit style
+with the normal style and the handling of such mixed styles may be subject
+to future change\&.
+.PP
+If arguments remain unused after formatting, the format string is reused
+until all arguments have been consumed\&. With the \fBprint\fP builtin, this
+can be suppressed by using the \fB\-r\fP option\&. If more arguments are
+required by the format than have been specified, the behaviour is as if
+zero or an empty string had been specified as the argument\&.
+.RE
+.TP
+.PD 0
+\fBpushd\fP [ \fB\-sLP\fP ] [ \fIarg\fP ]
+.TP
+.PD 0
+\fBpushd\fP [ \fB\-sLP\fP ] \fIold\fP \fInew\fP
+.TP
+.PD
+\fBpushd\fP [ \fB\-sLP\fP ] {\fB+\fP|\fB\-\fP}\fIn\fP
+Change the current directory, and push the old current directory
+onto the directory stack\&.  In the first form, change the
+current directory to \fIarg\fP\&.
+If \fIarg\fP is not specified, change to the second directory
+on the stack (that is, exchange the top two entries), or
+change to \fB$HOME\fP if the \fBPUSHD_TO_HOME\fP
+option is set or if there is only one entry on the stack\&.
+Otherwise, \fIarg\fP is interpreted as it would be by \fBcd\fP\&.
+The meaning of \fIold\fP and \fInew\fP in the second form is also
+the same as for \fBcd\fP\&.
+.RS
+.PP
+The third form of \fBpushd\fP changes directory by rotating the
+directory list\&.  An argument of the form `\fB+\fP\fIn\fP' identifies a stack
+entry by counting from the left of the list shown by the \fBdirs\fP
+command, starting with zero\&.  An argument of the form `\fB\-\fP\fIn\fP' counts
+from the right\&.  If the \fBPUSHD_MINUS\fP option is set, the meanings
+of `\fB+\fP' and `\fB\-\fP' in this context are swapped\&.
+.PP
+If the option \fBPUSHD_SILENT\fP is not set, the directory
+stack will be printed after a \fBpushd\fP is performed\&.
+.PP
+The options \fB\-s\fP, \fB\-L\fP and \fB\-P\fP have the same meanings as for the
+\fBcd\fP builtin\&.
+.RE
+.TP
+\fBpushln\fP [ \fIarg\fP \&.\&.\&. ]
+Equivalent to \fBprint \-nz\fP\&.
+.TP
+\fBpwd\fP [ \fB\-rLP\fP ]
+Print the absolute pathname of the current working directory\&.
+If the \fB\-r\fP or the \fB\-P\fP flag is specified, or the \fBCHASE_LINKS\fP
+option is set and the \fB\-L\fP flag is not given, the printed path will not
+contain symbolic links\&.
+.TP
+\fBr\fP
+Same as \fBfc \-e \-\fP\&.
+.TP
+.PD 0
+\fBread\fP [ \fB\-rszpqAclneE\fP ] [ \fB\-t\fP [ \fInum\fP ] ] [ \fB\-k\fP [ \fInum\fP ] ] [ \fB\-d\fP \fIdelim\fP ]
+.TP
+.PD
+ [ \fB\-u\fP \fIn\fP ] [ \fIname\fP[\fB?\fP\fIprompt\fP] ] [ \fIname\fP \&.\&.\&.  ]
+Read one line and break it into fields using the characters
+in \fB$IFS\fP as separators, except as noted below\&.
+The first field is assigned to the first \fIname\fP, the second field
+to the second \fIname\fP, etc\&., with leftover
+fields assigned to the last \fIname\fP\&.
+If \fIname\fP is omitted then
+\fBREPLY\fP is used for scalars and \fBreply\fP for arrays\&.
+.RS
+.PP
+.PD 0
+.TP
+.PD
+\fB\-r\fP
+Raw mode: a `\fB\e\fP' at the end of a line does not signify line
+continuation and backslashes in the line don't quote the following
+character and are not removed\&.
+.TP
+\fB\-s\fP
+Don't echo back characters if reading from the terminal\&.  Currently does
+not work with the \fB\-q\fP option\&.
+.TP
+\fB\-q\fP
+Read only one character from the terminal and set \fIname\fP to
+`\fBy\fP' if this character was `\fBy\fP' or `\fBY\fP' and to `\fBn\fP' otherwise\&.
+With this flag set the return value is zero only if the character was
+`\fBy\fP' or `\fBY\fP'\&.  Note that this always reads from the terminal, even
+if used with the \fB\-p\fP or \fB\-u\fP or \fB\-z\fP flags or with redirected input\&.
+This option may also be used within zle widgets\&.
+.TP
+\fB\-k\fP [ \fInum\fP ]
+Read only one (or \fInum\fP) characters\&.  All are assigned to the first
+\fIname\fP, without word splitting\&.  This flag is ignored when \fB\-q\fP is
+present\&.  Input is read from the terminal unless one of \fB\-u\fP or \fB\-p\fP
+is present\&.  This option may also be used within zle widgets\&.
+.TP
+\fB\-z\fP
+Read one entry from the editor buffer stack and assign it to the first
+\fIname\fP, without word splitting\&.  Text is pushed onto the stack with
+`\fBprint \-z\fP' or with \fBpush\-line\fP from the line editor (see
+\fIzshzle\fP(1))\&.  This flag is ignored when the \fB\-k\fP or \fB\-q\fP flags are present\&.
+.TP
+.PD 0
+\fB\-e\fP
+.TP
+.PD
+\fB\-E\fP
+The input read is printed (echoed) to the standard output\&.  If the \fB\-e\fP
+flag is used, no input is assigned to the parameters\&.
+.TP
+\fB\-A\fP
+The first \fIname\fP is taken as the name of an array and all words are
+assigned to it\&.
+.TP
+.PD 0
+\fB\-c\fP
+.TP
+.PD
+\fB\-l\fP
+These flags are allowed only if called inside a
+function used for completion (specified with the \fB\-K\fP flag to
+\fBcompctl\fP)\&.  If the \fB\-c\fP flag is given, the words of the
+current command are read\&. If the \fB\-l\fP flag is given, the whole
+line is assigned as a scalar\&.  If both flags are present, \fB\-l\fP
+is used and \fB\-c\fP is ignored\&.
+.TP
+\fB\-n\fP
+Together with \fB\-c\fP, the number of the word the cursor is on is
+read\&.  With \fB\-l\fP, the index of the character the cursor is on is
+read\&.  Note that the command name is word number 1, not word 0,
+and that when the cursor is at the end of the line, its character
+index is the length of the line plus one\&.
+.TP
+\fB\-u\fP \fIn\fP
+Input is read from file descriptor \fIn\fP\&.
+.TP
+\fB\-p\fP
+Input is read from the coprocess\&.
+.TP
+\fB\-d\fP \fIdelim\fP
+Input is terminated by the first character of \fIdelim\fP instead of
+by newline\&.
+.TP
+\fB\-t\fP [ \fInum\fP ]
+Test if input is available before attempting to read\&.  If \fInum\fP
+is present, it must begin with a digit and will be evaluated
+to give a number of seconds, which may be a floating point number;
+in this case the read times out if input is not available within this
+time\&.  If \fInum\fP is not present, it is taken to be zero, so that
+\fBread\fP returns immediately if no input is available\&.
+If no input is available, return status 1 and do not set any variables\&.
+ 
+This option is not available when reading from the editor buffer with
+\fB\-z\fP, when called from within completion with \fB\-c\fP or \fB\-l\fP, with
+\fB\-q\fP which clears the input queue before reading, or within zle where
+other mechanisms should be used to test for input\&.
+ 
+Note that read does not attempt to alter the input processing mode\&.  The
+default mode is canonical input, in which an entire line 