RE: prj.el under source control
Title: prj.el under source control Nascif , I've had similar problems using CVS on a previous JDEE version. The problem was I added the prj.el files as a text file whereas under certain conditions it might contain binary characters (such as when specfying a control key in the key bindings) that CVS considered as end-of-file marker, and thus truncated the file. After modifying the file attribute to binary, this worked again. I hope this can help, Guillaume. -Original Message-From: Nascif Abousalh-Neto [mailto:[EMAIL PROTECTED]]Sent: mardi 19 novembre 2002 22:29To: [EMAIL PROTECTED]Subject: prj.el under source control Hi, I recently added our prj.el files to source control (clearcase) but soon after that I start to get some strange behavior - basically related to loss of customizations, like modeline, font-lock, key bindings, and project name. I'm not sure it is related, but I'm thinking that the fact that fact that the prj.el is now read-only may be causing problems. Could that be the case? Another variable: I recently migrated from jde2.2.9beta10 to jde2.2.9. I tried to move back but the problem persisted. Regards, Nascif PS: Still no comments on my previous question on how to have subprojects appending to paths defined on parent projects, instead of just overriding then...
RE: prj.el under source control
Title: Message Hi Guillaume, That is a very good hint, I'll keep an eye for that. Thanks, Nascif -Original Message-From: Guillaume Berche [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 21, 2002 3:14 AMTo: Abousalh-Neto, Nascif [NCRTP:3X50:EXCH]; [EMAIL PROTECTED]Subject: RE: prj.el under source control Nascif , I've had similar problems using CVS on a previous JDEE version. The problem was I added the prj.el files as a text file whereas under certain conditions it might contain binary characters (such as when specfying a control key in the key bindings) that CVS considered as end-of-file marker, and thus truncated the file. After modifying the file attribute to binary, this worked again. I hope this can help, Guillaume. -Original Message-From: Nascif Abousalh-Neto [mailto:[EMAIL PROTECTED]]Sent: mardi 19 novembre 2002 22:29To: [EMAIL PROTECTED]Subject: prj.el under source control Hi, I recently added our prj.el files to source control (clearcase) but soon after that I start to get some strange behavior - basically related to loss of customizations, like modeline, font-lock, key bindings, and project name. I'm not sure it is related, but I'm thinking that the fact that fact that the prj.el is now read-only may be causing problems. Could that be the case? Another variable: I recently migrated from jde2.2.9beta10 to jde2.2.9. I tried to move back but the problem persisted. Regards, Nascif PS: Still no comments on my previous question on how to have subprojects appending to paths defined on parent projects, instead of just overriding then...
Re: prj.el under source control
Nascif == Nascif Abousalh-Neto [EMAIL PROTECTED] writes: Nascif Hi, Nascif I recently added our prj.el files to source control Nascif (clearcase) but soon after that I start to get some strange Nascif behavior - basically related to loss of customizations, like Nascif modeline, font-lock, key bindings, and project name. I'm not Nascif sure it is related, but I'm thinking that the fact that fact Nascif that the prj.el is now read-only may be causing Nascif problems. Could that be the case? Nascif Another variable: I recently migrated from Nascif jde2.2.9beta10 to Nascif jde2.2.9. I tried to move back but the problem persisted. Do you have templates with CVS keywords in them? If so when you check the prj.el out, they will get expanded, and it will all go horribly pear shaped. There are a couple of ways around this. My normal solution is to set the flag which stops keyword expansion. Phil
RE: prj.el under source control
Henrik Kjær writes: Hi Tom I don't think your problem relates to Nascif (see ealier), but I have also experienced problem with project settings since moving from 2.2.9.beta12 to 2.2.9. Mine are related to make settings. Make has now got its own menu point under options, and strangely enough these settings is not saved in the project file when saving project. Anyway, at present I have moved my make settings out of my prj.el file and into my .emacs and everything works ok - BUT I can only do this as I at present only are working on one project, so somehow the problem has to be solved - I think it is a bug in the new jde!? This is indeed a regression bug in JDE 2.2.9. I made a change in this release such that several packages are not loaded into memory until you execute one of the package's commands. This is intended to reduce the startup time for the JDEE. Unfortunately, some time ago another JDEE maintainer changed the project file system to build the list of variables that need to be changed only once, when the JDEE is initially loaded. Thus variables defined by packages loaded later are not saved by the project file subsystem. The jde-make package is one of those packages. The fix is straightforward. I will make the fix this evening and upload a patched JDE 2.2.9 this evening to the JDEE website. - Paul
Re: prj.el under source control
Nascif Abousalh-Neto [EMAIL PROTECTED] writes: PS: Still no comments on my previous question on how to have subprojects appending to paths defined on parent projects, instead of just overriding then... I haven't looked at the code to do this, but I imagine this would be a fairly easy fix. And I think it's a good suggestion. I'll see if I can produce a patch soon.
Re: prj.el under source control
Actually, I think I misread your question. I thought you were asking if multiple prj.el files could be in affect at once - so that on going to a file, we would walk from the root directory to the current directory, executing each prj.el in between. If we do this (who knows, JDE may do it already), then you could easily do what you want, just put in your prj.el (add-to-list 'jde-global-classpath this/project/dir), etc. I think this may be frowned upon, since all setting of variables should come through customizations, but it should work. IMHO, we shouldn't have this policy where things have to be customized instead of just set, it seems against the free-wheeling nature of elisp. Nascif Abousalh-Neto [EMAIL PROTECTED] writes: Thanks, appreciated. Maybe a special symbol meaning the contents of the same variable as defined in a parent (or default) prj.el would do the trick... So you could have jde-global-classpath = ($BASE_VALUE this/project/dir) -Original Message- From: Andrew Hyatt [ mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Tuesday, November 19, 2002 4:56 PM To: Abousalh-Neto, Nascif [NCRTP:3X50:EXCH] Cc: [EMAIL PROTECTED] Subject: Re: prj.el under source control Nascif Abousalh-Neto [EMAIL PROTECTED] writes: PS: Still no comments on my previous question on how to have subprojects appending to paths defined on parent projects, instead of just overriding then... I haven't looked at the code to do this, but I imagine this would be a fairly easy fix. And I think it's a good suggestion. I'll see if I can produce a patch soon.
RE: prj.el under source control
Hi Tom I don't think your problem relates to Nascif (see ealier), but I have also experienced problem with project settings since moving from 2.2.9.beta12 to 2.2.9. Mine are related to make settings. Make has now got its own menu point under options, and strangely enough these settings is not saved in the project file when saving project. Anyway, at present I have moved my make settings out of my prj.el file and into my .emacs and everything works ok - BUT I can only do this as I at present only are working on one project, so somehow the problem has to be solved - I think it is a bug in the new jde!? MVH Henrik Kjær -Original Message- From: Tom Eskridge [mailto:[EMAIL PROTECTED]] Sent: 19. november 2002 22:54 To: Nascif Abousalh-Neto; [EMAIL PROTECTED] Subject: Re: prj.el under source control I have been getting the same behavior since switching to 2.2.9. It may be more likely to be a jde issue than a source control issue. On Tuesday 19 November 2002 03:28 pm, Nascif Abousalh-Neto wrote: Hi, I recently added our prj.el files to source control (clearcase) but soon after that I start to get some strange behavior - basically related to loss of customizations, like modeline, font-lock, key bindings, and project name. I'm not sure it is related, but I'm thinking that the fact that fact that the prj.el is now read-only may be causing problems. Could that be the case? Another variable: I recently migrated from jde2.2.9beta10 to jde2.2.9. I tried to move back but the problem persisted. Regards, Nascif PS: Still no comments on my previous question on how to have subprojects appending to paths defined on parent projects, instead of just overriding then... -- Cheers, Tom Tom Eskridge Institute for Human and Machine Cognition University of West Florida 40 S. Alcaniz St Pensacola, FL 32501 ph: 850-202-4454 fx: 850-202-4440
