variables set in prj.el bleeding thru to custom.el
Paul == Paul Erion [EMAIL PROTECTED] writes: Paul I have some variables being set in a prj.el file (e.g., Paul 'jde-run-application-class') and only there. But when I Paul exit XEmacs and look in '~/.xemacs/custom.el', well, there Paul they are. Is this standard behaviour, or am I messing up Paul somewhere? Most likely the latter. Please describe the exact steps that you used to set the variables in the project file so we can try to reproduce the problem. Paul Paul I'm using JDE 2.3.3 and XEmacs 21.4.13 on WinXP Paul Pro. This isn't a big deal, but it's not what I expected. Paul Thanks, Paul Paul Paul __ Do you Yahoo!? New Paul Yahoo! Photos - easier uploading and sharing. Paul http://photos.yahoo.com/
Re: variables set in prj.el bleeding thru to custom.el
Oops, I don't really remember how I initially created prj.el -- it was a while ago. I just happened to be looking over my ~/.xemacs/custom.el file and noticed that variables that were being set in prj.el were also being (unexpectedly) set in custom.el. And deleting them (via editing) from custom.el did not make them go away (that is, the code to set those variables kept reappearing). If it's any help, I've included the contents of prj.el (which resides in the directory ~/../Projects/WordDance/). (jde-project-file-version 1.0) (jde-set-variables '(jde-ant-interactive-buildfile ~/../Projects/WordDance/Development/build.xml) '(jde-global-classpath (quote (~/../Projects/WordDance/class))) '(jde-db-source-directories (quote (~/../Projects/WordDance/source/main/ ~/../Projects/WordDance/source/generated/ $JAVA_HOME/src))) '(jde-run-application-class com.mv.worddance.gc.WordDanceApp) '(jde-run-working-directory ~/../Projects/WordDance/Deployment/) ) --- Paul Kinnucan [EMAIL PROTECTED] wrote: Paul == Paul Erion [EMAIL PROTECTED] writes: Paul I have some variables being set in a prj.el file (e.g., Paul 'jde-run-application-class') and only there. But when I Paul exit XEmacs and look in '~/.xemacs/custom.el', well, there Paul they are. Is this standard behaviour, or am I messing up Paul somewhere? Most likely the latter. Please describe the exact steps that you used to set the variables in the project file so we can try to reproduce the problem. Paul Paul I'm using JDE 2.3.3 and XEmacs 21.4.13 on WinXP Paul Pro. This isn't a big deal, but it's not what I expected. Paul Thanks, Paul Paul __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/
Re: variables set in prj.el bleeding thru to custom.el
Paul == Paul Erion [EMAIL PROTECTED] writes: Paul Oops, I don't really remember how I initially created Paul prj.el -- it was a while ago. I just happened to be Paul looking over my ~/.xemacs/custom.el file and noticed that Paul variables that were being set in prj.el were also being Paul (unexpectedly) set in custom.el. And deleting them (via Paul editing) from custom.el did not make them go away (that Which is of course exactly not the way to delete them. The code in custom.el is automatically generated, depending on the settings of customization variables. Any edits that you make to the file will be overwritten by XEmacs next time you customize a variable, using the XEmacs customization interface. Paul is, the code to set those variables kept reappearing). If Paul it's any help, I've included the contents of prj.el (which Paul resides in the directory ~/../Projects/WordDance/). You must follow the procedure outlined in the JDEE User's Guide to set JDEE variables. If you have any questions about the procedure, feel free to ask. Paul
Re: variables set in prj.el bleeding thru to custom.el
On Mon, 22 Dec 2003 11:51:27 -0800 (PST), Paul Erion wrote: Oops, I don't really remember how I initially created prj.el -- it was a while ago. I just happened to be looking over my ~/.xemacs/custom.el file and noticed that variables that were being set in prj.el were also being (unexpectedly) set in custom.el. And deleting them (via editing) from custom.el did not make them go away (that is, the code to set those variables kept reappearing). *if* you want to edit custom.el, do it outside emacs (and when no emacs is open). Usually its is a better idea to do M-x customize-variable your-variable and then select erase customization (you should not have opened any JDE-mode files while you do that so that you do not mess up any prj.el files) to remove entries from your custom.el. HTH, Michael
variables set in prj.el bleeding thru to custom.el
I have some variables being set in a prj.el file (e.g., 'jde-run-application-class') and only there. But when I exit XEmacs and look in '~/.xemacs/custom.el', well, there they are. Is this standard behaviour, or am I messing up somewhere? I'm using JDE 2.3.3 and XEmacs 21.4.13 on WinXP Pro. This isn't a big deal, but it's not what I expected. Thanks, Paul __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/
