On Thu, Jan 31, 2008 at 10:22:05PM -0500, A. Costa wrote: > Found some typos in '/usr/share/man/man1/zshmodules.1.gz', see attached > '.diff'. > > Hope this helps...
> --- zshmodules.1 2008-01-29 10:24:59.000000000 -0500 > +++ /tmp/zshmodules.1 2008-01-31 06:22:11.000000000 -0500 > @@ -856,7 +856,7 @@ > key names are the macros defined in the \fBcurses\&.h\fP or \fBncurses\&.h\fP > with the prefix `\fBKEY_\fP\&' removed; see also the description of the > parameter \fBzcurses_keycodes\fP below\&. Other keys cause a value to be > -set in \fIparam\fP as before\&. On a succesful return only one of > +set in \fIparam\fP as before\&. On a successful return only one of > \fIparam\fP or \fIkparam\fP contains a non\-empty string; the other is set > to an empty string\&. > .PP > @@ -1388,7 +1388,7 @@ > Note that it is possible to achieve exactly the same effect as the > \fBzsh/newuser\fP module by adding code to \fB/etc/zshenv\fP\&. The module > exists simply to allow the shell to make arrangements for new users without > -the need for invervention by package maintainers and system administrators\&. > +the need for intervention by package maintainers and system administrators\&. > .PP > The script supplied with the module invokes the shell function > \fBzsh\-newuser\-install\fP\&. This may be invoked directly by the user > @@ -1691,7 +1691,7 @@ > consists of the scheduled time in seconds since the epoch > (see the section `The zsh/datetime Module\&' for facilities for > using this number), followed by a colon, followed by any options > -(which may be empty but will be preceeded by a `\fB\-\fP\&' otherwise), > +(which may be empty but will be preceded by a `\fB\-\fP\&' otherwise), > followed by a colon, followed by the command to be executed\&. > .RS > .PP Index: Doc/Zsh/mod_curses.yo =================================================================== RCS file: /cvsroot/zsh/zsh/Doc/Zsh/mod_curses.yo,v retrieving revision 1.22 diff -u -r1.22 mod_curses.yo --- Doc/Zsh/mod_curses.yo 12 Nov 2007 12:16:52 -0000 1.22 +++ Doc/Zsh/mod_curses.yo 1 Feb 2008 19:33:33 -0000 @@ -143,7 +143,7 @@ key names are the macros defined in the tt(curses.h) or tt(ncurses.h) with the prefix `tt(KEY_)' removed; see also the description of the parameter tt(zcurses_keycodes) below. Other keys cause a value to be -set in var(param) as before. On a succesful return only one of +set in var(param) as before. On a successful return only one of var(param) or var(kparam) contains a non-empty string; the other is set to an empty string. Index: Doc/Zsh/mod_newuser.yo =================================================================== RCS file: /cvsroot/zsh/zsh/Doc/Zsh/mod_newuser.yo,v retrieving revision 1.3 diff -u -r1.3 mod_newuser.yo --- Doc/Zsh/mod_newuser.yo 21 May 2007 11:32:03 -0000 1.3 +++ Doc/Zsh/mod_newuser.yo 1 Feb 2008 19:33:33 -0000 @@ -36,7 +36,7 @@ Note that it is possible to achieve exactly the same effect as the tt(zsh/newuser) module by adding code to tt(/etc/zshenv). The module exists simply to allow the shell to make arrangements for new users without -the need for invervention by package maintainers and system administrators. +the need for intervention by package maintainers and system administrators. The script supplied with the module invokes the shell function tt(zsh-newuser-install). This may be invoked directly by the user Index: Doc/Zsh/mod_sched.yo =================================================================== RCS file: /cvsroot/zsh/zsh/Doc/Zsh/mod_sched.yo,v retrieving revision 1.5 diff -u -r1.5 mod_sched.yo --- Doc/Zsh/mod_sched.yo 14 Jun 2007 13:25:58 -0000 1.5 +++ Doc/Zsh/mod_sched.yo 1 Feb 2008 19:33:33 -0000 @@ -53,7 +53,7 @@ (see ifnzman(The zsh/datetime Module)\ ifzman(the section `The zsh/datetime Module') for facilities for using this number), followed by a colon, followed by any options -(which may be empty but will be preceeded by a `tt(-)' otherwise), +(which may be empty but will be preceded by a `tt(-)' otherwise), followed by a colon, followed by the command to be executed. The tt(sched) builtin should be used for manipulating the events. Note -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
