At 10:58 AM 12/15/00 -0500, Sam Steingold wrote:
>> * In message <[EMAIL PROTECTED]>
>> * On the subject of "RE: java file parsing frequency"
>> * Sent on Fri, 15 Dec 2000 13:49:17 GMT
>> * Honorable Paul Kinnucan <[EMAIL PROTECTED]> writes:
>>
>> At 12:34 PM 12/14/00 -0500, Michaud, Ben A. wrote:
>> >
>> >I have this in my .emacs, but it does not seem to work:
>> >(setq jde-auto-parse-enable nil)
>>
>> Won't work.
>>
>> You MUST use Emacs' customization facility, e.g.,
>> M-x customize-variable
>
>you might prefer
>
>(custom-set-variables
> '(jde-auto-parse-enable nil))
>
>in your .emacs instead of the setq form (which is ignored by JDE) and
>instead of the interactive custom (which is a waste of time).
Interactive custom is an automatic code generation facility that generates
setup code automatically in your .emacs file, thereby eliminating
configuration errors caused by typos and value type violations. In my
experience, it is much faster to set a variable in a customizatin buffer
than it is to first determine what type of value the variable should be set
to (e.g., is it a string or a list of strings), then write the setq form
and then test it to make sure that it works.
Of course, if you never forget a paren and can determine instantly from a
Lisp variable's name what its type is, maybe writing the code yourself is
faster.
Interestingly, before interactive custom, most problems reported by JDE
users were caused by setting variables to the wrong type. Since custom,
those kinds of errors have virtually disappeared. For this reason, I
consider interactive custom a great saver of MY time, if not yours.
- Paul
- Paul
- Paul
