Re: Problems debugging files with more than 1000 lines.

fre, 2004-11-19 kl. 08:40 skrev Morten: tor, 2004-11-18 kl. 08:23 skrev Morten / Datagruppen MultiMED: ons, 2004-11-17 kl. 22:21 skrev Javier S. Lopez: Morten [EMAIL PROTECTED] writes: ons, 2004-11-17 kl. 14:05 skrev Javier S. Lopez: This has been fixed since version 2.3.4beta4

Re: Problems debugging files with more than 1000 lines.

Hi Morten, It's possible there is a regression. I will take a look this evening to see if I can reproduce the problem. Just to be sure, which debugger are you using? The JDEE's interface to jdb or JDEbug? Paul Morten writes: fre, 2004-11-19 kl. 08:40 skrev Morten: tor, 2004-11-18 kl.

Re: Problems debugging files with more than 1000 lines.

man, 2004-11-22 kl. 13:24 skrev Paul Kinnucan: It's possible there is a regression. I will take a look this evening to see if I can reproduce the problem. Just to be sure, which debugger are you using? The JDEE's interface to jdb or JDEbug? Thanks, I apologize in advance, in case it should

Re: Problems debugging files with more than 1000 lines.

man, 2004-11-22 kl. 13:31 skrev Morten: man, 2004-11-22 kl. 13:24 skrev Paul Kinnucan: It's possible there is a regression. I will take a look this evening to see if I can reproduce the problem. Just to be sure, which debugger are you using? The JDEE's interface to jdb or JDEbug? CUT

navigation from backtrace

I've searched various bits of documentation without any luck -- is there a mouse click or command from jde and/or ecb which works on a backtrace line in a compilation/run window, so that if I hit an exception under c-C c-V c-R, w/o the debugger, I can get to the offending source line easily?

Re: Problems debugging files with more than 1000 lines.

Morten / Datagruppen MultiMED [EMAIL PROTECTED] writes: man, 2004-11-22 kl. 13:31 skrev Morten: man, 2004-11-22 kl. 13:24 skrev Paul Kinnucan: It's possible there is a regression. I will take a look this evening to see if I can reproduce the problem. Just to be sure, which debugger

Re: Java Buffer modified on reading

I don't know when this started happening, but I have noticed that loading any Java buffer creates lots of Wrong type argument: integer-or-marker-p, nil errors in the *Messages* buffer. While that doesn't halt loading of the buffer for me (which is what leaves the buffer marked modified), I

Buffer is read-only: #buffer *compilation*

Hi, Using GNU Emacs CVS, JDE 2.3.4, CEDET 1.0beta3b. When trying to compile code with C-C C-V C-C, I am getting the following error: save-excursion: Buffer is read-only: #buffer *compilation* This happens every time - I think I have tried almost every combination of customize variables (at

Why does JDEE look for tools.jar

Hi, I'm having trouble running JDEE (with both Emacs and XEmacs) on a Debian GNU/Linux system. The problem is with finding the tools.jar file. Since I'm using runtimes not licensed from Sun (sablevm, kaffe etc.) this file is missing. Could some one explain to me (just a hint) why tools.jar is

Re: Buffer is read-only: #buffer *compilation*

Anderson, Timothy K [EMAIL PROTECTED] writes: Hi, Using GNU Emacs CVS, JDE 2.3.4, CEDET 1.0beta3b. When trying to compile code with C-C C-V C-C, I am getting the following error: save-excursion: Buffer is read-only: #buffer *compilation* This looks familiar... I had the problem when

Re: Why does JDEE look for tools.jar

Suraj Acharya writes: JDE also looks for tools.jar to check if a directory is a JDK directory or not. Try creating an empty tools.jar in the lib directory of your JDK. You will be able to use the compile server, but it might let you used JDE with other jdks. The JDEE currently assumes