Re: Questions

[thaynes ca ibm com]

Michael T. Babcock wrote:
> If you want to make something useful, make a series of commands that
> interpret whole-word commands into actual unix command-lines for use with
> voice recognition software.
>
> Saying "list files in slash usr slash lib" is easier than "spell
> L-S-SPACE-SLASH KEY-U-" ... ;-)
>
> All that needs doing is writing programs by the names of things like
"list"
> and "open" and "run" which interpret the command lines after them and
exec
> the interpreted result.
>
> "list files in home" -- ls ~
> "open file number three" -- take 3rd file from listing, check mime exec
and
> run it or give error.

If you are going to go that way with typed commands, go all the way and
make a
universal natural language interface and tie it into whatever inputs you
care
to use, be it typing, handwriting recognition or speech. You would then
have a
natural language parser that would perform a fuzzy probability-based
analysis
of what you said/wrote/typed against a known list of possible commands and
then
executed the relevant shell command. This would need a sanity filter to
stop
you doings like saying 'erm after slash' to your word processor and seeing
your
home directory disappear as the parser pushes 'rm -rf /' to your shell.

Cheers,
Toby Haynes