Is "command" working right, yet?

[Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>]

command [ -pvV ]
     The command word is taken to be the name of an external command,
     rather than a shell function or builtin.   If the POSIX_BUILTINS
     option is set, builtins will also be executed but certain special
     properties of them are suppressed. The -p flag causes a default
     path to be searched instead of that in $path. With the -v flag,
     command is similar to whence and with -V, it is equivalent to
     whence -v.

Prelimnaries:

I've created my own "true" at the head of $path to be able to distinguish
the builtin from the external command.  It just echoes EXTERNAL, like so:

burner% disable true
burner% true
EXTERNAL

First let's talk about option parsing.

burner% command -p -V true
zsh: command not found: -V
burner% command -V -p true
command: bad option: -p
burner% command -pv true
zsh: command not found: -pv

Those options can be combined in both bash and ksh.  Setting posixbuiltins
makes no difference to zsh:

burner% setopt posixbuiltins
burner% command -p -V true
zsh: command not found: -V
burner% command -V -p true  
command: bad option: -p

I think this is pretty clearly a bug.

The next question has to do with builtins and path search.  There was a
long thread about this on the austin-group (POSIX standards) list several
weeks ago and I'm still not sure what the final outcome implies.  The
issue is the circumstances in which builtins are allowed to mask commands
in $PATH. Starting over with a fresh "zsh -f" so the builtin is enabled
and NO_POSIX_BUILTINS, "command" runs the external but "command -p" runs
the builtin:

burner% command true
EXTERNAL
burner% command -p true
burner% 

The latter seems a little odd to me, but I suppose that means that when
the doc says "a default path" it means one with builtins implicitly at the
front?  However, it relates to the last question:

Using the versions available on my Ubuntu desktop, and default $PATH, all
of bash, ksh, and zsh with POSIX_BUILTINS, execute the builtin for both
"command" and "command -p".  Anybody know if that's correct?  If it is,
how does one force the use of the external command in [the forthcoming]
POSIX?  (If it involves magic syntax in $PATH, I can't assert that zsh
is going to adopt it, but I'd still like to know the answer.)