V12 Help Nits

[samintz]

The "What's New" section in the help file states:

The default directory for the Command Prompt window is now set to the
selected directory in the Folders view. (This allows tab completion in
the Command Prompt window to match the List View when no path is
specified.)

I believe that should state "Command Input" window not "Command Prompt"
window.

-Scott

 

[samintz]

The new DO syntax is not documented very clearly. I assume the following
was meant to be a short-hand version of expressing:
DO [WHILE | UNTIL [DATETIME yyyy-mm-dd hh:mm:ss]] condition (commands)

DO WHILE condition
DO UNTIL condition
DO UNTIL DATETIME yyyy-mm-dd hh:mm:ss


The /P switch works just fine in my testing of command line DO. Was it
left out on purpose or just missed?

DO varname IN [range] [/I"text"] [/D"path" /N[dj] /O:[-]adegnrstu /Sn]
[/A:[[-][+]rhsdaecjot] [/C /L /T"..."] [@]set (commands)

-Scott

samintz <> wrote on 08/18/2010 10:31:12 AM:

> The "What's New" section in the help file states:
>
> The default directory for the Command Prompt window is now set to the
> selected directory in the Folders view. (This allows tab completion in
> the Command Prompt window to match the List View when no path is
> specified.)
>
> I believe that should state "Command Input" window not "Command Prompt"
> window.
>
> -Scott
>
>
>
>
>
>

 

[rconn]

The /P switch works just fine in my testing of command line DO. Was it
left out on purpose or just missed?

DO varname IN [range] [/I"text"] [/D"path" /N[dj] /O:[-]adegnrstu /Sn]
[/A:[[-][+]rhsdaecjot] [/C /L /T"..."] [@]set (commands)
samintz <> wrote on 08/18/2010 10:31:12 AM:

I'm not sure what you're referring to -- /P is not a new switch, and has never been in the quick help (as with several dozen other obscure options). It is documented on the DO command page in the help.

 

[samintz]

I was referring to the help on the "What's New" help page.
-Scott

rconn <> wrote on 08/18/2010 12:38:44 PM:

> ---Quote (Originally by samintz)---
> The /P switch works just fine in my testing of command line DO. Was it
> left out on purpose or just missed?
>
> DO varname IN [range] [/I"text"] [/D"path" /N[dj] /O:[-]adegnrstu /Sn]
> [/A:[[-][+]rhsdaecjot] [/C /L /T"..."] [@]set (commands)
> samintz <> wrote on 08/18/2010 10:31:12 AM:
> ---End Quote---
>
> I'm not sure what you're referring to -- /P is not a new switch, and
> has never been in the quick help (as with several dozen other
> obscure options). It is documented on the DO command page in the help.
>
>
>
>

 

[samintz]

The "What's New" help for DO explicitly states "The syntax is:" and then
goes on to list a handful of DO expressions. If the new command-line DO
is supposed to support the full DO syntax then perhaps a simpler example
of:

DO loop_control (commands)

with a link to the full DO explanation in the help would be better. As
it's stated, I get the impression that only the listed syntax is "legal"
even though other syntax like /P works.

It might also be beneficial to show the command-line DO syntax on the DO
help page in addition to just describing the syntax.

Format: DO loop_control

commands

[ITERATE]

commands

[LEAVE [n]]

commands

ENDDO

or

DO loop_control (commands)


-Scott

samintz <> wrote on 08/18/2010 12:57:42 PM:

> I was referring to the help on the "What's New" help page.
> -Scott
>
> rconn <> wrote on 08/18/2010 12:38:44 PM:
>
>
>
> ---Quote---
> > ---Quote (Originally by samintz)---
> > The /P switch works just fine in my testing of command line DO. Was it

> > left out on purpose or just missed?
> >
> > DO varname IN [range] [/I"text"] [/D"path" /N[dj] /O:[-]adegnrstu /Sn]

> > [/A:[[-][+]rhsdaecjot] [/C /L /T"..."] [@]set (commands)
> > samintz <> wrote on 08/18/2010 10:31:12 AM:
> > ---End Quote---
> >
> > I'm not sure what you're referring to -- /P is not a new switch, and
> > has never been in the quick help (as with several dozen other
> > obscure options). It is documented on the DO command page in the

help.

> >
> >
> >
> >
> ---End Quote---
>
>
>

 

[rconn]

> I was referring to the help on the "What's New" help page.

"What's New" has never had full syntax descriptions, only enough to point
someone to the *real* documentation if they want details.