How do I submit my patch for non-english locale jdb debugging?
Hi I once wrote this list regarding a problem debugging code with more than 999 lines with the jdb mode in JDE, using the danish locale. I ended up being able to construct a patch for the code myself, by asking a lot of questions in #Emacs on the freenode IRC-network. I wonder if the proposed patch I posted earlier has been incorporated into JDE in some way. cvs diff suggests otherwise, so I wonder how to submit the patch. Obviously I would be interested in the patch making it to the official release, so I don't have to patch the code myself on subsequently updates. Cheers, Morten .
Re: first time emacs and JDE --having problem with JDE Configuration
man, 2004-12-06 kl. 03:58 skrev Sharif Sharif M: i am having problem of configuring JDE. i have installed emacs latestone as well as JDE latest one .. can anyone tell me step by step what i need to do to install all the packegs and where i will be copying all the packegs. thank you so much in advance.. Well, assuming that GNU/Emacs is installed properly, I give you the URL to install JDE: http://jdee.sunsite.dk/install.html I hope it proves helpfull! Cheers, Morten .
Re: Problems debugging files with more than 1000 lines.
Hi I had my first attempt at writing emacs LISP yesterday, so please bear with me, if the patch isn't complete. I haven't tested this patch extensively, but I tried the code after the change, and it seemed to work for me. As Javier noted, maybe the code should examine the locale, and then only match the char that the local uses, but I have no idea how to write such code. Anyway .. here is a cvs diff from lisp-directory of the latest cvs version of jde: Index: jde-jdb.el === RCS file: /pack/anoncvs/jde/lisp/jde-jdb.el,v retrieving revision 1.45 diff -r1.45 jde-jdb.el 356c356 \\] .*(\\([^\$\n]*\\).*:\\([0-9]*,?[0-9]+\\))) --- \\] .*(\\([^\$\n]*\\).*:\\([0-9]*[^[:digit:]]?[0-9]+\\))) 676c676 ^.*: thread=.*, \\(\\(.*[.]\\)*\\)\\([^\$]*\\)\\(\$.*\\)*[.].+(), line=\\([0-9,]*\\),) --- ^.*: thread=.*, \\(\\(.*[.]\\)*\\)\\([^\$]*\\)\\(\$.*\\)*[.].+(), line=\\([0-9,.]*\\),) 1192c1192 ^.*: \thread=.*\, \\(\\(.*[.]\\)*\\)\\([^$]*\\)\\($.*\\)*[.].+(), line=\\([0-9,]*\\))) --- ^.*: \thread=.*\, \\(\\(.*[.]\\)*\\)\\([^$]*\\)\\($.*\\)*[.].+(), line=\\([0-9,.]*\\))) 1873c1873 (if (string-match , number) --- (if (string-match [^[:digit:]] number) Please tell me if you want me to supply this in a different format, and how I do that, if so. Kind regards, and thanks for a great java mode for Emacs, Morten B. Isaksen .
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 cut cut Not sure what to to tell you. Is is possible that the old version is getting loaded somehow. I would be rather surprised if that was the case. When I click the jde menu, and hold the mouse over help, it displays jde 2.3.4. Is there another way of testing which version of JDE I am running? It seems strange that I get the error that has been fixed ... Morten . Now I have deleted all other other versions of CEDET and JDE that I could find. I tried to remove the path in .emacs, and jde refused to load. I checked the sourcecode, and there are comments in the changelog about the problem with linenumber 999. I wonder if a specific version of java or something else might be required? I use j2sdk 1.4.2_01. I'm running GNU/Linux Debian sarge (and I purged both CEDET and jde from the system, so that I only use the files I downloaded). Please tell me what I can do to find out whats wrong with my system, since Javier seems to have no problem, I assume its my setup! Kind regards, Morten .
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 be some stupid installation error on my hand. I'm using the jdb. Sincerely, Morten .
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 I'm using the jdb. I noticed that in the code, it checks for , .. and replaces it with . However, in my locale, lines past 999, are /not/ shown as : 1,204 .. they're show as 1.204 as we use , in fractional numbers. Eg. in danish, 1½ is 1,5 not 1.5 .. so 1,204 would be between the first and the second line. Now in regex, . matches any char, so I guess it needs to be escaped with \ or something? (I am not proficient with lisp or elisp). Morten .
Re: Problems debugging files with more than 1000 lines.
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 cut cut Not sure what to to tell you. Is is possible that the old version is getting loaded somehow. I would be rather surprised if that was the case. When I click the jde menu, and hold the mouse over help, it displays jde 2.3.4. Is there another way of testing which version of JDE I am running? It seems strange that I get the error that has been fixed ... Morten .
RE: semantic error
Hi,
I have previously tried to track that error down and I came up with a
way of reproducing the error:
class TestClass {
private boolean aSomeFlag;
boolean isEnabled() {
return aSomeFlag;
}
}
If you delete the parentheses of the isEnabled method, then wait for the
automatic reparse done by semantic, then delete the next two characters
without semantic doing reparse in between, the error occurs.
File when error occurs:
class TestClass {
private boolean aSomeFlag;
boolean isEnabl {
return aSomeFlag;
}
}
However, since upgrading semantic to the latest version 14 (no beta) I
have not been able to reproduce this error. I think that Eric Ludlam may
have
been mingling with the auto-parse features of semantic since the spontaneous
C-l behaviour previously mentionened on the JDEE mailing list also seems to
have disappeared. . The two 'features' may somehow have been interrelated
since
they apparently both appeared in connection with some reparse.
Hence my advise is to upgrade to the lastest version of semantic.
/Morten
-Original Message-
From: mark a foltz [mailto:[EMAIL PROTECTED]]
Sent: 7. august 2002 19:00
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: semantic error
hello,
while editing files in jde, occasionally the font-lock dies and a stack
overflow in equals error is reported in the message buffer. this seems
to happen when editing method bodies, but it's hard to tell. in this
case i was doing a search-replace and the replace target was in a method
body.
i applied the patch posted earlier in this list to semantic-imenu.el to
try and fix the problem, but no avail. david ponce's overlay-fix.el
also doesn't apply since i'm using emacs 21.
emacs: 21.2.1
jde: 2.2.9beta10
semantic: 1.4beta14
speedbar: 0.14beta3
eieio: 0.17beta4
backtrace and .emacs are attached.
i can send the code snippet too if that helps.
best,
m.
--
mark a foltz -*- mit ai lab -*- [EMAIL PROTECTED] -*- 617.253.8926
