Re: JDE 1.43: kill-line broken after upgrade
Maybe this will help, concerning updating JDEE via the XEmacs packaging system: Usually this simply doesn't work for me. I can't quite remember what errors I get, but Wrong type argument sounds familiar :) Anyway, what I do is download the Pre-release versions of semantic, speedbar etc using the XEmacs packager (they're usually up to date). Then I download the JDEE latest version from the site, and install it manually like the XEmacs packager would do (this means, in two seperate dirs for the java files and lisp files, as explained somewhere on the site). Warning: I just like this solution cause then I can still use the packager if I would want to - you pbb avoid lots of problems if you just follow the instructions on the site. However, and here's the interesting part, I have to remove any compiled lisp files from the jde dir to make it work. Even if I just install the (usually outdated) JDEE package using XEmacs, it still gives errors if I use the compiled version. This gives some interesting issues when using apt-get upgrade when it tries to install a new xemacs version ;) I basically just remove the .elc files from the lisp/jde dir after that. dunno if my ramblings are in any way helpful - to summarize, I'd say try removing the .elc files from your jde install dir and see what that does. Kurt Paul Kinnucan wrote: otisg writes: Hello, I just upgraded my JDE to version 1.43 (via the built-in stuff in the Options menu). I am using XEmacs on RH 7.3, installed from the RPM (xemacs-21.4.6-7). After I upgraded I noticed that I can no longer do C-k (kill-line). The error message that I get is: Wrong type argument: extentp, nil I get the same error if I hit the DEL key or if I try to kill a marked region with C-w. Is this a known problem? No. What should I do to fix this? Don't know. You don't give enough information. If you want my help, submit a full problem report, including your XEmacs init file and a backtrace of the error. Is something in the new JDE hogging these keys or something similar? No. The JDEE does not hog reserved keys. - Paul
Re: AW: jde and j2ee ...thanks giving !
Steering those talking about Java discussions toward new (or recently added) JDEE features, could be a good plan. Oh, for Andres original post about EJB design, I suggest taking a look at the ant integration functions offered by the JDEE and also look into using XDoclet with Ant. (And using templates to help with some of the in-source tag generation.) Not sure if those things were suggested. Most of the discussion seems to have happened in a thread that did not reach me. On Wed, 5 Feb 2003, [EMAIL PROTECTED] wrote: From the JavaDEE website: The JavaDEE mailing list provides a technical support, design, and news forum for JavaDEE. It has more than 600 members. If you are having problems setting up or using the JavaDEE, would like to propose and discuss enhancements, or simply be advised of the latest JavaDEE developments, this is the place to turn. Nothing in there about talking about Java.
RE: JDE 1.43: kill-line broken after upgrade
--- Andy Piper [EMAIL PROTECTED] wrote: On another note 21.4.6 is _old_. The current release is 21.4.11, you should probably upgrade if you can. 21.4.11? HA! That's _ancient_! Ya gots to keep up with the times. .12 was released a few days after .11. hehe -- Le __ Post your free ad now! http://personals.yahoo.ca
cc-mode indenting
Hi, This is the current indentation style: code gmo.options = MQC.MQGMO_WAIT | MQC.MQGMO_FAIL_IF_QUIESCING | MQC.MQGMO_SYNCPOINT | MQC.MQGMO_CONVERT; /code I would like: code gmo.options = MQC.MQGMO_WAIT | MQC.MQGMO_FAIL_IF_QUIESCING | MQC.MQGMO_SYNCPOINT | MQC.MQGMO_CONVERT; /code The context (C-c C-s) of the second line is statement-cont, which is the same as any other statement continuation, so I think another specialized context has to be created. Is this doable? Also I remember there is something for Emacs that will align multiple lines at =, does someone know the package name? Thanks. -- Le __ Post your free ad now! http://personals.yahoo.ca
Re: cc-mode indenting
At 11:42 AM 2/6/2003 -0500, Le Wang wrote: Hi, This is the current indentation style: code gmo.options = MQC.MQGMO_WAIT | MQC.MQGMO_FAIL_IF_QUIESCING | MQC.MQGMO_SYNCPOINT | MQC.MQGMO_CONVERT; /code I would like: code gmo.options = MQC.MQGMO_WAIT | MQC.MQGMO_FAIL_IF_QUIESCING | MQC.MQGMO_SYNCPOINT | MQC.MQGMO_CONVERT; /code What I do in this case is rewrite it as gmo.options = (MQC.MQGMO_WAIT | MQC.MQGMO_FAIL_IF_QUIESCING | MQC.MQGMO_SYNCPOINT | MQC.MQGMO_CONVERT); The parentheses change the context, so that it formats it like you want. Probably not the best solution, but it's one that works. Troy Troy Daniels [EMAIL PROTECTED] 781-273-3388 x218
