Just a couple of things others missed...
On Mon, 19 Jun 2000 14:04:03 GMT, Martin Kift wrote:
>2. I noticed that the latest JDE has help at point functionality, but the
>docs say it needs jdk documentation in javadoc format I believe? Are these
>downloadable, or do they have to be generated somehow? Also, is it possible
>to get JDK to reference the jdk HTML's instead?
Just a point - I think the jdk HTMLs you are referring to *are* javadoc
format. Javadoc creates html files from comments in your source code, and
this is how the standard java documentation is built. If you are unsure,
have a look at the html source - it will have a comment "created by
javadoc" near the top.
Note that you can look up javadoc generated pages for *any* java class,
even ones you have created yourself, if you have jde configured right. The
process JDE uses to find a class is :
1. It runs a Java routine which uses RTTI to find all classes in your
classpath that end in the class that is under point. For example, if the
point is on "Array" it will find "java.lang.reflect.Array" and
"java.sql.Array".
2. If there is more than one matching class, it prompts you for the one you
want to view.
3. It then looks for a file with a .html extension, and a path that matches
the full class name, under each directory you have specified in the
'jde-help-docsets' setting. For example, for java.sql.Array it will look
for "java/sql/Array.html" under each directory you have specified. (i.e on
my system, it looks for "d:/dev/java/jdk/docs/api/java/sql/Array.html" etc)
So, if you want your own classes to show up, make sure they are in your
classpath, and make sure their documentation is in the right subdirectory
structure, and Bob's your mother's brother.
(I'm rather familiar with this procedure myself, as I had to dig into it to
find why I couldn't look up java3d classes. It turns out I had to add all
the .jar files for java3d to my classpath, as JDE can't automatically find
them.)
>5. When I edit the .emacs file, is there anyway of getting emacs to realise
>the changes without shutting it down, or is that the only options?
Someone else said this as well, but it's worth repeating - you can compile
a single statement from your .emacs file by pressing Ctrl-Meta-x while the
point is somewhere in the statement. This is great for debugging your
.emacs file - just run each statement in turn until you find the problem...
-Korny
--
life is like an analogy...
-- Kornelis Sietsma [EMAIL PROTECTED] www.sietsma.com/korny icq:2039172
