If the macros you want to add just type ordinary keystrokes (no control
characters or backslashes or enter keys, for example, but <,@@, and many
others are fine) then you can just enter them in the topic editor,
specifying a different written form. (The NaturallySpeaking
documentation refers to these words or phrases as "dictation shortcuts"
rather than as macros. You should be able to find some more information
on them in the online help under Adding Words under Creating
Personalized Vocabulary Topics. These shortcuts will be available
whenever the topic to which you have added them is active, including
when you use natural text to dictate directly into another window.
> 2) Also, where/how do I add vi and Unix macros? If I do this, then are
> they available to me under natural text in a Unix window?
> Thanks in advance. I find the NaturallySpeaking documentation totally
> inadequate. Wish they bring up to the level of DragonDictate
> documentation and either supply hardcopy or make it easy for us to print
> a PostScript version of the complete document.
> Nancy
>
For Vi and Unix macros, you probably only want them to be available in
certain contexts. Given that it usually takes me about 15 seconds to
switch topics, and that I switch back and forth between different Unix
and non-Unix Windows frequently, creating a Unix topic doesn't seem to
make sense. Instead, you can create these macros with the New Command
Wizard. The Wizard will give you the option of making these macros
global, or specific to a particular application. If you always use the
same telnet program to work in Unix, you can make them specific to that
application. You also have the option to make them specific to a
particular string contained in the window title. If you can't count on
a particular string always being in the window title, then just delete
all the characters in that field. On the other hand, if you are using
vim (vi improved, which I strongly recommend) and an X terminal emulator
(such as exceed), which will change the window title to something
including "vim", then you could use that feature to make sure that your
vi commands are not active when you are not editing a file.
Even fancier things are possible (for example, having FORTRAN macros
available only when the window title includes the string ".f77") but
would take more work to set up.
David Fox
davidfox@@fas.harvard.edu
http://cfa-www.harvard.edu/~dcfox/index.html
--------------------------------------------------
Well, well! It cannot be helped, and it is difficult not to slip in
talking to a dragon, or so I have always heard.
-- Balin, The Hobbit, J. R. R. Tolkien
![]() |