http://jde.sunsite.dk/
JDE 2.2.7beta10
***
* PLEASE READ *
***
* *
Hi Eric,
Yes, I have seen this double quote phenomenon myself. Must be a regression
error in the many changes to the project code in the last several beta
releases. I'll look into it.
- Paul
At 01:09 PM 4/21/2001 -0700, Eric D. Friedman wrote:
I'm doing some testing of the 2.2.7b9 release. I
From: Paul Kinnucan [mailto:[EMAIL PROTECTED]]
Sent: Saturday, April 21, 2001 10:38 PM
Subject: Re: bug in writing prj.el files
Hi Eric,
Yes, I have seen this double quote phenomenon myself. Must be a regression
error in the many changes to the project code in the last several beta
In message [EMAIL PROTECTED], "Eric D. Friedman" w
rites:
:
: Using FSF emacs (will try xemacs shortly) and 2.2.7b10, I was able to
: debug the test code I wote about earlier.
OK, I tried xemacs and it does *not* work. Using top, sorted by
CPU usage, I see several java processes (which
Now I upgraded to jdk 1.3.1 RC-1 and my test case works with xemacs.
The release notes for jdk 1.3.1 say that there were problems with
the JPDA in 1.3 + hotspot, and I know that Optimizeit didn't work with
hotspot VMs before 1.3.1, so perhaps JDEbug is a victim of the same bugs?
At any rate, I
In message [EMAIL PROTECTED], Paul Kinnucan write
s:
: Eric, I am a little confused. Are you saying that my thread priority "fix"
: in beta10 is an improvement? If so, that is very interesting. I believer
: there other debugger threads that JDEbug sets to max priority (actually
:
In message [EMAIL PROTECTED], eric writes:
:
: Yes, the beta10 fix yielded a working debugger in both emacsen. There
: were no changes to code or to the number of ambient processes between
: the upgrade, and I repeated the exercise with a downgrade (didn't work)
: and a re-upgrade (worked).
At 08:49 PM 4/22/2001 -0400, [EMAIL PROTECTED] wrote:
Hi there,
System :
- Suse 7.0 Linux
- Emacs 20.7.1
- java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0)
Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-2623 (JIT
enabled: jitc))
- prj.el is
At 09:32 PM 4/22/2001 -0700, you wrote:
: This is very helpful. Is this true of both Linux and Windows or are you
: able to test only Linux?
Linux only - I would've tested Solaris too but my company moved to a new
office over the weekend and the network isn't back up yet.
I realized that I
