Re: Upgrading suggestions

[Ken Goldman <kgold@watson.ibm.com>]

I confess that I use the 'if it isn't broken, don't fix it' approach.

Like you, I have a collection of ancient customizations.  I only remove 
them when something breaks, which is rare.

On 10/4/2011 1:28 PM, Perry Smith wrote:
> I thought I would toss out this question to this group.
>
> Over time, hacks and tweaks that I've added to my emacs init files
> get incorporated into the official release (usually with a much
> better implementation).  I assume I'm not unique in this area.
>
> How do others, when moving up to a new level of emacs, deal with
> this?  How do you (or perhaps you don't bother) find the things that
> have moved into the production version and start using those versions
> rather than the old version that you have.  e.g. ruby mode is now
> part of the distribution.  There are countless examples of this.
>
> The biggest example I have is all of the "customize" features.  I
> still have old lisp code that is setting things up using old setq's
> instead of the new customized stuff.  That seems to work ok but sorta
> bothers me.
>
> Thanks, pedz
>
>
>