At 01:46 PM 8/19/99 -0400, Thomas McKay wrote:
>OS: NT4.0
>JDE: 2.1.6beta5
>Emacs: 20.4.1
>JPDA: 1.0rc1
>JDK: 1.2.2-W
>
>I have my shell set to 'c:/bin/tcsh' in my .emacs file and SHELL set to
>the same thing in my .cshrc file. When I run 'M-x grep' from emacs I
>get the expected results, namely in the buffer named *grep* is the
>output of the grep command. However, once I set a breakpoint via the
>JDEbug menu and then run JDE->Debug App, the grep command now brings up
>a shell titled 'c:/bin/tcsh.exe' while the grep command is running.
>Anyone know why this is?
>
>Also, it seems that JDEbug is using the PATH in my Control
>Panel->System->Environment for finding things. Why isn't it using my
>.cshrc file values? Until I set the PATH variable there to include the
>jpda1.0rc1/bin dir things didn't start at all. Now I get "no such file
>or directory, javaw" message in the minibuffer when I run JDE->Debug
>App.
>
>Could this have to do with relying on the bash shell. (I can't say that
>I even know what that is. :-)
>
The JDE launches JDEBug directly via the Emacs start-process function. In other
words, it does not use a shell to start the debugger. That explains why your
csh path setting has no effect. As for the seeming interaction between the JDE
and grep, I have no clue, as the JDEBug interface uses neither grep nor
a shell.
- Paul
