You can probably guess my next question. Where do I find out
which variables need to be changed in this release (or, in general,
any release)? I looked in the ReleaseNotes.txt and that doesn't seem
to be the definitive place.
*OR*, does JDE adversely react upfront so that I'll know exactly
which variables need to be changed? Because the phrase "any variable
that appears to be broken" might suggest that there may be a few
which need to be changed but I wouldn't normally know it.
*OR*, is the prj.el migration so insignificant that I shouldn't
worry too much right now. And if worse comes to worse, I'll just
start from scratch and retype every customization variable back in.
BTW, excellent product.
Gary F.
>From: Paul Kinnucan <[EMAIL PROTECTED]>
>
>At 07:26 PM 7/20/00 GMT, gary fong wrote:
> >I believe I read in one of these emails which flew by that
> >the 2.1.8 prj.el file can't be used with 2.1.9, correct?
> >If that's the case, how do I migrate my existing 2.1.8 prj.el
> >files to 2.1.9?
> >
>
>I just open a customization buffer for any variable that appears to be
>broken, reset the variable to its standard setting, close the buffer,
>reopen it, set it to the setting I want, and resave the project file. For
>example, jde-key-bindings is one of the most commonly broken variables,
>usually because new commands with new keybindings have been added.
>Restoring jde-key-bindings to its "standard" setting updates the variable
>to the new settings in the current release.
>
>- Paul
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
