ANNOUNCE: Mozilla Development Environment for Emacs (MDEE) created.
I would like to announce the creation of the MDEE projects for Mozilla and Emacs
development.
http://mdee.mozdev.org
Right now we have made some very good progress but we would like to see more
people using the software and potentially see more developers joining the
project.
See the website and mailing list for more information.
--
Kevin A. Burton ( [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] )
Location - San Francisco, CA, Cell - 415.595.9965
AIM - sfburtonator, Web - http://www.peerfear.org/
GPG fingerprint: 4D20 40A0 C734 307E C7B4 DCAA 0303 3AC5 BD9D 7C4D
IRC - openprojects.net #infoanarchy | #p2p-hackers | #reptile
$live{free} || die "";
RE: jde-global-classpath error
I think if anybody is going to be able to help you, you need to provide a lot more information. Use the JDE/Help/Submit Problem Report menu function. / Petter > -Original Message- > From: Jeba Bhaskaran [mailto:[EMAIL PROTECTED]] > Sent: den 14 januari 2003 18:20 > To: [EMAIL PROTECTED] > Subject: jde-global-classpath error > > > I am using jde-global-classpath variable. When > compiling, JDE only uses the last part of the path. > For example, C:\jars\test.jar comes out as -classpath C:/test.jar. > > __ > Do you Yahoo!? > Yahoo! Mail Plus - Powerful. Affordable. Sign up now. > http://mailplus.yahoo.com >
jde-global-classpath error
I am using jde-global-classpath variable. When compiling, JDE only uses the last part of the path. For example, C:\jars\test.jar comes out as -classpath C:/test.jar. __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
Order of function/hooks executed when JDE mode is entered
Hi, I'm using JDE 2.3.2 on XEmacs 21.4.11 (Win32 native). I noticed that stuff I set in a function that's added to the jde-mode-hook is being overwritten (by some defaults I'd think.) Can someone please shed some light on what order which hooks/functions are called when JDE mode is entered? TIA, Christian Schmitt
AW: Buffer Kill
Hmmm, I took a look at it again, and you're right... It seems that there is more code being run after the jde-mode-hook (that's where I do (remove-hook 'jde-ant-build-hook 'jde-compile-finish-kill-buffer) that adds the function to the hook again. What I do now is remove the hook from my project file and that does work. Hth, Christian > -Ursprüngliche Nachricht- > Von: Raul Acevedo [mailto:[EMAIL PROTECTED]] > Gesendet: Montag, 13. Januar 2003 22:07 > An: Schmitt, Christian (ext.) > Betreff: AW: Buffer Kill > > > That didn't seem to work... > > Schmitt, Christian (ext.) wrote: > > > > > -Ursprüngliche Nachricht- > > Von: Inger, Matthew [mailto:[EMAIL PROTECTED]] > > Gesendet: Freitag, 10. Januar 2003 19:14 > > An: '[EMAIL PROTECTED]' > > Betreff: Buffer Kill > > > > > > > is there a way to turn off the buffer kill after > compilation completion? > > > I've tried customizing the jde-compile-finish-hook > variable both with > > > jde-set-variables and with custom-set-variables, but > neither one works. > > > It's annoying if i have split buffer windows, then try > to compile one of > > > the files, that it kills the completion buffer, and > unsplits the window > > > automatically. That is truly obnoxious, and i can't > seem to figure out > > how > > > to turn it off. > > > > Try this: (remove-hook 'jde-ant-build-hook > 'jde-compile-finish-kill-buffer) > > > > > > Hth, > > Christian >
AW: JDEbug - Show debug frame on XEmacs
No offense taken :-) I'm sure there's a one liner that might take care of it, but my Lisp knowledge (so far ;-) is too limited so I haven't found it yet. Christian > -Ursprungliche Nachricht- > Von: Andrew Hyatt [mailto:[EMAIL PROTECTED]] > Gesendet: Montag, 13. Januar 2003 18:19 > An: Schmitt, Christian (ext.) > Cc: [EMAIL PROTECTED] > Betreff: Re: JDEbug - Show debug frame on XEmacs > > > > Sorry, I don't meet to imply that your workaround isn't good. But > maybe there's an xemacs make-frame-names-alist equivalent, so it could > be a one line change. > > Andrew Hyatt <[EMAIL PROTECTED]> writes: > > > Your problem sounds unsurprising. Like a lot of brand new jde code, > > it is not tested on xemacs. Thanks for bringing this to my > attention, > > I'll see if there is a good workaround (those more familiar with > > xemacs please let me know if you know this), else I'll use something > > like your workaround. > > > > "Schmitt, Christian (ext.)" > <[EMAIL PROTECTED]> writes: > > > >> Hi, > >> today I used JDEbug for the first time. I clicked on "Show > debug frame" in > >> the "JDEbug" menu > >> which didn't work on XEmacs 21.4.11 [Win32 native] (JDE > 2.3.2) with an > >> error, that > >> 'make-fram-names-alist function definition is void. > >> > >> Now I don't know if there's an XEmacs equivalent to this function. > >> Right now I work around it by putting this in my .emacs: > >> ; > >> ; XEmacs does not have 'make-fram-names-alist > >> ; so we define it when it's not there. > >> ; Source is taken from GNU Emacs' frame.el where > >> ; function 'frame-parameter (in GNU Emacs) hase been > >> ; replaced by 'frame-property > >> ; > >> (if (not (fboundp 'make-frame-names-alist)) > >> (defun make-frame-names-alist () > >> (let* ((current-frame (selected-frame)) > >> (falist > >> (cons > >>(cons (frame-property current-frame 'name) > current-frame) > >> nil)) > >> (frame (next-frame nil t))) > >> (while (not (eq frame current-frame)) > >> (progn > >> (setq falist (cons (cons (frame-property frame > 'name) frame) > >> falist)) > >> (setq frame (next-frame frame t > >> falist)) > >> ) > >> > >> > >> Cheers, > >> Christian Schmitt >
