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. > > > >
