Roger:
> "DOG is a DOS SHELL, or command interpreter. DOG works on
> most, if not all flavors of DOG."
>
> So, this is pun at DOS for being a dog? ;-) This is found
> on the Github page.
>
> Think you meant to state, "DOG is a DOS shell or command
> interpreter. DOG shell works on most, if not all flavors
> of DOS."
`shell', being a normal noun, should indeed not spelled in
uppercase, but the comma after `shell' need not have been
removed, if the author used it to denote a pause of
pondering before an explanation, cf. the punctuation in the
following titles:
Frankenstein; or, The Modern Prometheus
Moby-Dick; or, The Whale
There is no problem with a comma after `or'. But another
comma is actually missing -- the one after the parenthetical
expression "if not all", so the second sentence should read:
DOG works on most, if not all, flavors of DOS.
Some more errors in the online manual:
1. When working with DOG in the prompt you typically use
the internal and external commends, and other programs.
Here, a comma is missing after `prompt', and `commands'
is written with a typo of `e' for `a'.
2. These internal commands are built-in to the DOG binary
`built-in' is an adjective. Say "are built into".
3. It has the same effect as if you would have typed the
expansion.
Simplify: "as if you typed".
4. In DOG directories are executable:
A comma is missing after `DOG'.
5. HH alone simply lists the DOG commands.
Much better: "displays a list of all DOG commands"
(without the article).
6. Name or path of EMPTY directory to remove.
An indefinite artcile is missing before `directory':
"of an empty directory".
7. PATH - A list of directories used to search for
commands. Paths in the list are separated by the ;
character.
the list of paths where to search for commands. The
paths are separated by the ; character.
8. Exit the current DOG shell. Works only if the shell is
not a primary shell.
The grammar is good, but what is the effect in the
primary shell? Probably no effect all, which should be
documented, e.g.:
Exit the current DOG shell, unless it is the primary
shell, in which case the command has no effect (or shows
an error?).
9. Without parameters BP puts ASCII character 07h into
stdout, causing a beep as long as the ANSI driver is
loaded.
A comma is missing after `parameters', and the reference
to the ANSI driver makes no sense: as long as what
duration?
10. DT dispolays the current date and time.
Typo in `dispolays'.
I wonder whether the effect of a command should be descirbed
/before/ its syntax and parameters, so that the reader
should understand the context of what he is reading.
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
