At 11:05 PM 3/29/00 +0100, you wrote:
>
>
>>>>>> "Paul" == Paul Kinnucan <[EMAIL PROTECTED]> writes:
>
>
> Paul> When you execute a compile (or run, or debug) command, the JDE
> Paul> constructs a -classpath argument by concatenating the paths in
> Paul> the list that is the value of jde-global-classpath. I am
> Paul> proposing that when the JDE constructs the classpath argument,
> Paul> it scans each path for environment variables, e.g., strings
> Paul> between % characters on Windows, and replaces them with the
> Paul> result of applying getenv, e.g., getenv("classpath").
>
> Yeah that seems fair enough to me, as it should be clear from
>the custom buffer what is going to happen when you compile or
>whatever.
>
> >> 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.
>
> Paul> The JDE could insert the unexpanded version of the classpath
> Paul> in the compile buffer while passing the expanded value to the
> Paul> create-process function, e.g., in the above example, the
> Paul> compile buffer would contain:
>
>
> >> path going "why isnt it changing". Possibly it should be
> >> mentioned in the global class path that other variables can
> >> silently over ride it?).
>
>
> Paul> Possibly people should read the doc.
>
> Good heavens Paul, what a terrible things to suggest...
I know. Sometimes I just like to say things purely for their shock value.
>
> Paul> The fact that jde-global-classpath can be overridden by
> Paul> jde-compile-option-classpath, etc. is mentioned both in the
> Paul> JDE User's Guide and in the docstrings for the variables in
> Paul> question.
>
> Yes I've just released that it is mentioned in the docstring
>of jde-global-classpath, which I had missed. I think I missed it
>because it does not mention the overriding variables by name, rather
>just saying "The JDE also allows you to set classpaths individually for
>the compile, run, and debug command".
>
> The other way around the documentation says "This option overrides
>the `jde-global-classpath' option." which means that its value is a
>click away. It might be good to emphasise this in the global-classpath
>documentation. Say...
>
> "*Specify class paths for compile, run, and debug commands.
>Unless overridden by `jde-compile-option-classpath',
>`jde-run-option-classpath' this option specifies [etc etc]"
>
>
> Its just a thought. I tend to feel that its better
>to be really obvious about things, rather than rely on users to
>actually read the documentation, as they never do. Even when they are
>programmers who could probably be induced to rant about "users who
>never read the documentation" under other circumstances.
>
I agree this doc string is vague. It needs to be revised as you suggest
(which I will do). A lot of the current doc was written in haste in the
early days and never revised to keep up with changes. I plan to do some
serious updating and revising in the next few months. That is why I really
am serious when I post doc that I think answers a user's question and then
ask what is not clear. The answer will help me to do the revisions.
Thanks for your suggestions.
Regards,
Paul
------------------------------------------------------------
ASKING FOR TECHNICAL SUPPORT ON THE JDE LIST
Please use the JDE->Help->Submit Problem Report command when reporting a
bug or seeking help. This command generates a complete snapshot of your
system. Submitting such a snapshot increases the chances that your request
will get a swift response.
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
JDE website: http://sunsite.auc.dk/jde/
JDE mailing list archive:
http://www.mail-archive.com/[email protected]/maillist.html
