RE: Semantic 1.4beta11
Can someone forward this to the ecb-list
(mailto:[EMAIL PROTECTED]), our mail server has this address
blacklisted.
Thanks,
Jeff
-Original Message-
From: Jeff Rancier [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 27, 2001 11:14 AM
To: Jde-List; ecb-list; Ntemacs (E-mail)
Subject: Semantic 1.4beta11
Hello,
I installed the new package, and tried it on a C header file. I have
several:
typedef struct
{
blah,
blah,
blah
} blah_S;
like definitions in the file. The *ECB Methods* buffer shows a:
^@
for each. It looks like:
--
^@
^@
^@
^@
^@
[Variables][+]
--
Anyone else seen this?
Thanks,
Jeff
Terrorist Attacks on U.S. - How can you help?
Donate cash, emergency relief information
http://dailynews.yahoo.com/fc/US/Emergency_Information
RE: Semantic 1.4beta11
I installed the new package, and tried it on a C header file. I have
several:
typedef struct
{
blah,
blah,
blah
} blah_S;
like definitions in the file. The *ECB Methods* buffer shows a:
^@
for each. It looks like:
--
^@
^@
^@
^@
^@
[Variables][+]
--
Anyone else seen this?
Yes, me too.
It´s not a problem of ECB but of semantic; speedbar shows the same output.
Eric, do you know why this happens?
Klaus
Re: Debug error
/ Paul Kinnucan [EMAIL PROTECTED] was heard to say: | Which version of the JDK are you using? 1.2.2 on Linux. Be seeing you, norm -- Norman Walsh [EMAIL PROTECTED] | [They] say the Earth is flat, but I http://nwalsh.com/| know that it is round, for I have seen | the shadow on the moon, and I have more | faith in a shadow than in | [them].--Ferdinand Magellan
Re: Debug error
/ Paul Kinnucan [EMAIL PROTECTED] was heard to say: | Norman Walsh writes: | / Paul Kinnucan [EMAIL PROTECTED] was heard to say: | | Which version of the JDK are you using? | | 1.2.2 on Linux. | | Does setting jde-db-debugger to oldjdb help? Thanks, Paul. That helped (some). I now get further: cd /projects/sun/resolver/ jdb -classpath /usr/local/jaxp-1.1/jaxp.jar:/projects/apache/xml-xerces/java/build/classes:/projects/sun/resolver/.classes:/home/ndw/java xread /sourceforge/docbook/xcatalog Initializing jdb... Deferring breakpoint xread.main. It will be set after the class is loaded. run xread /sourceforge/docbook/xcatalog VM Started: Set deferred breakpoint request xread:22 Line 22 is the first assignment statement at the top of the main method. Unfortunately, that breakpoint is apparently never encountered. It just hangs. Be seeing you, norm -- Norman Walsh [EMAIL PROTECTED] | 'I have done that,' says my memory. 'I http://nwalsh.com/| cannot have done that'--says my pride, | and remains adamant. At last--memory | yields.--Nietzsche
Re: Debug error
Norman Walsh writes: / Paul Kinnucan [EMAIL PROTECTED] was heard to say: | Norman Walsh writes: | / Paul Kinnucan [EMAIL PROTECTED] was heard to say: | | Which version of the JDK are you using? | | 1.2.2 on Linux. | | Does setting jde-db-debugger to oldjdb help? Thanks, Paul. That helped (some). I now get further: cd /projects/sun/resolver/ jdb -classpath /usr/local/jaxp-1.1/jaxp.jar:/projects/apache/xml-xerces/java/build/classes:/projects/sun/resolver/.classes:/home/ndw/java xread /sourceforge/docbook/xcatalog Initializing jdb... Deferring breakpoint xread.main. It will be set after the class is loaded. run xread /sourceforge/docbook/xcatalog VM Started: Set deferred breakpoint request xread:22 Line 22 is the first assignment statement at the top of the main method. Unfortunately, that breakpoint is apparently never encountered. It just hangs. Okay, I was hoping that the problem was that the default version of jdb with Linux JDK 1.1.2 is oldjdb. It appears to be the new jdb. Try renaming the oldjdb in the JDK bin directory to jdb (after renaming jdb to something else). That might at least get you going with the old version of jdb. Meanwhile, when I have some time, I'll see if I can guess why you were getting the Lisp error with new jdb. - Paul
Re[2]: Semantic 1.4beta11
Berndl, Klaus [EMAIL PROTECTED] seems to think that:
I installed the new package, and tried it on a C header file. I have
several:
typedef struct
{
blah,
blah,
blah
} blah_S;
like definitions in the file. The *ECB Methods* buffer shows a:
^@
for each. It looks like:
--
^@
^@
^@
^@
^@
[Variables][+]
--
Anyone else seen this?
Yes, me too.
It´s not a problem of ECB but of semantic; speedbar shows the same output.
Eric, do you know why this happens?
Klaus
An addition into the grammar caused the wrong information to be placed
in as the typedef name. This will be fixed in beta 12.
Eric
--
Eric Ludlam: [EMAIL PROTECTED], [EMAIL PROTECTED]
Home: www.ultranet.com/~zappoSiege: www.siege-engine.com
Emacs: http://cedet.sourceforge.net GNU: www.gnu.org
RE: Problem with indent-new-comment-line
Hi Curtis, Thanks for digging this out. Perhaps Eric or David can comment. - Paul Curtis Clifton writes: -Original Message- From: Paul Kinnucan [mailto:[EMAIL PROTECTED]] Niranjan Rao writes: JDE Version 2.2.8 GNU Emacs 20.7.1 on NT 4.0 When I try to continue comment using indent-new-comment-line (Meta - J) command, JDE adds new comment line along with proper comment marks i.e. // \s-*\*/ Is this problem in my settings or bug in JDE Insert the following form (setq block-comment-end nil) into your jde hook function. I don't know who is setting it to \s-*\*/ or why. I don't think it's the JDE. I've experienced this problem as well. A quick grep of my *.el files yields the following: ./semantic-1.4beta8/semantic-java.el:(set (make-local-variable 'block-comment-end) \\s-*\\*/) This is in the function semantic-default-java-setup and is preceded by the comment ;; Needed by `semantic-find-doc-snarf-comment'. semantic-find-doc-snarf-comment is defined in semantic-util.el. I'm not sure, but it seems to me that semantic is using block-comment-end for other than its intended purpose. Quoting from its declaration in simple.el: *String to insert to end a new comment on a line by itself. Should be an empty string if comments are terminated by end-of-line. If nil, use `comment-end' instead. Semantic seems to be using the variable as a regexp pattern match (if my lisp reading is correct). -- Curt
RE: Problem with indent-new-comment-line
Thanks to David Ponce's suggestion its working fine. Once again, my thanks for everyone who promptly suggested way out. - Niranjan -Original Message- From: Paul Kinnucan [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 27, 2001 2:00 PM To: Curtis Clifton Cc: Paul Kinnucan; Niranjan Rao; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Problem with indent-new-comment-line Hi Curtis, Thanks for digging this out. Perhaps Eric or David can comment. - Paul
