options shenanigans in pre4

[Zefram <A.Main@xxxxxxxxxxxxxxxxx>]

I'm not going to provide actual patches for any of the things I point
out as needing fixing here.  They're all very minor issues, and the
patches are trivial.

The pre4 patch says:
[Doc/zshexpn.man]
>+ preceding the set of five substitutions mentioned above.
>+ is
>  .SH FILENAME EXPANSION

Where did that "is" come from?  It's obviously a typo, and should be
removed.

[Doc/zshoptions.man]
>! \fBSHIN_STDIN\fP (\-\fBs\fP, ksh: \-\fBs\fP)
>--- 467,473 ----
>! \fBSHIN_STDIN\fP (\-\fBs\fP)

{setopt ramble localoptions
Hmm, I didn't notice that ksh handled this differently from sh.  Maybe
we *do* need a third set of option letters, though this seems to be the
only actual incompatibility.  We might want to implement the ksh option
at some point too.
}

>+ \fBSH_OPTION_LETTERS\fP
>+ If this option is set the shell tries to interpret single letter options
>+ (which are used with \fBset\fP and \fBsetopt\fP) like \fIksh\fP does.
>+ This also affects the value of the \fB-\fP special parameter.

Virtually identical to a patch I was planning to produce after the pre4
release.  I was going to call it KSH_OPTION_LETTERS, though, because
the set of options it selects are emulating ksh, not sh.  The other
option names that refer to ksh or sh do get the right one, so you might
actually want to change this.

>+ .BR sh / ksh
>+ emulation set:
...
>+ \-\fBs\fP SHIN_STDIN

Should not now be included in this list.

[Src/builtin.c]
>!     emulate(*argv, ops['R']);

Once again we have exactly the same idea.

-zefram