>>>>> "Paul" == Paul Kinnucan <[EMAIL PROTECTED]> writes:
Paul> At 02:24 PM 3/29/00 -0500, you wrote:
>> We've been handling the classpath by setting the following in
>> prj.el file:
>>
>> '(jde-compile-option-classpath (list (getenv "CLASSPATH")
>> "c:/sourcepath"))
Paul> Actually, it wouldn't be too hard to do expand environment
Paul> variables in classpaths, using getenv, when constructing the
Paul> compile, run, and debug command lines.
If I can be so bold as to make a suggestion here I would
do it in the defcustom, so that you have a value menu which allows
"Use environment variable value" and then "any other value". I would
not want my environment variables accidentally overriding the custom
values. I also think that it would be confusing if the command line
were made up of values which were not actually what the custom buffer
said. (For instance I know many people who have got a little confused
by the jde-global-class-path which is over-ridden by
jde-compile-class-path, and sit there changing the global class path
going "why isnt it changing". Possibly it should be mentioned in the
global class path that other variables can silently over ride it?).
The only thing that I do not understand is why javac is not
using the environment var automatically which it should do by
itself. Is it because emacs is using a different internal shell (bash
for instance) to launch javac than used to launch emacs dos in this
case I would have thought? Has the CLASSPATH been set in your
.bash_profile?
Paul> I'll put this on my list of things to do.
Just out of curiosity Paul, how long is this list?
Phil
