At 09:39 PM 1/28/00 +0100, you wrote: >Hi Paul, > >To continue our discussion of yesterday, i agree that the customization >variables are perfect to strictly define customizable variables. It's >the user interface that i feel uncomfortable with, i keep searching >through page after page of customization stuff. > There are all kinds of ways to avoid browsing through customization groups: - Bind a key, say F6, to customize-variable. This allows you to instantly customize familiar variables, such as jde-global-classpath or c-basic-offset. - Use the JDE->Project->Options->General/Compile/Run/Debug commands to display the respective JDE customization variables grouped according to functionality. You can then use C-s to quickly find the variable you want to customize. - Use C-h v to display the current value of a variable and then if you need to change it, click on the customize button in the help buffer. No more searching needed. - Use the JDEbug->Preferences menu to display a customize buffer for all the debugger options. >Oh well, about the '.emacs' file and the disappearing 'JDEbug' menu >item. I've attached my (very tiny) .emacs file with JDE customization >stuff. As you suggested, i've changed the 'setq' with >'jde-set-variables'. > I most certainly did NOT suggest using jde-set-variables to set the values of the JDE variables. Here is what I actually said: "...you MUST use custom to set JDE variables in your .emacs file." I have tested using customize to store the JDEbug customizations in my .emacs file and it WORKS PERFECTLY, i.e., the JDEbug menu appears for apps that do not have a *.prj file. - Paul
