Second, use runemacs.exe, that's how you're supposed to start emacs in
Windows mode, rather than DOS mode. That's why you getting the extra
window, nothing to do with NaturallySpeaking. If you look at the
Emacs FAQ, you'll notice that it's a common problem.
Third, you might consider using Emacs server and Emacs client. I
think these work under NT and Windows 95, but I'm not sure. Use info
to read up on them: control-h i gets you into info.
>>>>> "AJ" == Adam Janin <janin@@cs.berkeley.edu> writes:
AJ> I'm having trouble with the "AppBringUp" command in NaturallySpeaking
AJ> Deluxe, specifically trying to bring up parts of the exceed X server and
AJ> Emacs for Windows NT. When I try:
AJ> AppBringUp "emacs", "c:\emacs\bin\emacs"
AJ> NaturallySpeaking brings up a shell window in addition to emacs. When I try:
AJ> AppBringUp "emacs"
AJ> NaturallySpeaking brings up a new emacs window every time I use the macro,
AJ> instead of switching to the existing emacs window. The same thing happens
AJ> with AppSwapWith.
AJ> I have been unable to figure out how to get it to work with X server at all.
AJ> Does anyone had any suggestions?
AJ> Thanks!
AJ> Adam Janin
AJ> janin@@cs.berkeley.edu
AJ> P.S. I had quite a bit of difficulty installing the upgrade. Be careful
AJ> to install NaturallySpeaking, as well as any programs you want to
AJ> "AppBringUp", in directories without long filenames or embedded spaces.
AJ> Also, liberal use of "Wait 50" seems to make a lot of scripts work which
AJ> otherwise fail.
AJ> AJ
![]() |