At 03:11 AM 2/27/00 -0800, you wrote: >> At 02:29 AM 2/27/00 -0800, you wrote: >> >Thanks, I'll fix the jdpa directory classpath. I thought I had taken >> >care of that. >> > >> >Backslashes didn't work well for me. They confuse bash. I believe I >> >read this on a JDE FAQ - to use unix paths consistently with bash >> >on windows. It works well for me compiling and running programs. >> > >> >> The FAQ only meant that you should use forward slashes, which is fine. But >> Windows has no concept of a root directory (AFAIK). You always need to >> include a drive specifier. I'd sure like to know how you are able to get a >> path >> >> /projects/ProjectX/project >> >> like to be accepted by Windows or a Windows application. I believe you are >> using the Cygnus toolset and, of course, Cygnus apps, such as bash, >> understand Unix paths. However, the Java vm on Windows is a Windows >> application and hence AFAIK only understands paths that begin with a drive >> specifier. > >I assume this is the same situation as when I run a program from >JDE, no? (Same as for compiling, too?) > No. You're assumption is wrong. The JDE uses the shell only to launch javac. All other executables are launched as direct subprocesses of Emacs itself. >In those cases, as I understand it, JDE feeds the unix-like >command line to bash, and bash fixes it up. > No, bash does not fix up paths. >Bash stores a "mount table" in the windows registry. I have >"mounted" c:\ as the "root". Thus a leading "/" gets translated to >"c:\". > Only for Cygnus applications. The only Cygnus app you are using is bash. bash does not do anything with values of command-line switches, e.g., -classpath. >I also have a HOME environment variable, which bash maps to "~", >but I don't have any tildes in my JDE or emacs configuration. > >This is how compilation and running works when launched from >JDE. Whether JDEbug can be expected to work the same way, I >don't know. > JDEbug is launched, using java.exe, and thus works in the same way as running any Java program under JDE but not the way you assumed it works. >The problem with using backslashes, as I understood it was that >you inevitably end up with mixed forward slashes and back slashes >on the same command line, which confuses bash. I had this No, that is not the primary reason for avoiding back slashes. >problem, even though I used backslashes exclusively everywhere. >Another user (perhaps I found this in the list archive) recommended >using forward slash exclusively, and this works well for me in >compiling and running. > You can use forward or backward slashes interchangeably in DOS/Windows paths. So why not use backward slashes? Because a backslash is the escape character in both Lisp and Java programs. By using forward slashes, you avoid having to double up slashes in paths and you avoid syntax errors when you forget to double up slashes. - Paul
