From: Ken Goldman <kgold@watson.ibm.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Upgrading suggestions
Date: Thu, 06 Oct 2011 15:19:10 -0400 [thread overview]
Message-ID: <j6kuve$6et$2@dough.gmane.org> (raw)
In-Reply-To: <C0729F91-44CC-4A84-B773-296A4579180D@gmail.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
>
>
>
next prev parent reply other threads:[~2011-10-06 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 17:28 Upgrading suggestions Perry Smith
2011-10-04 18:09 ` Jambunathan K
2011-10-04 20:32 ` S Boucher
2011-10-06 19:19 ` Ken Goldman [this message]
[not found] <mailman.5127.1317749352.939.help-gnu-emacs@gnu.org>
[not found] ` <87fwj8tadw.fsf@notengoamigos.org>
[not found] ` <j82j09$fun$3@reader1.panix.com>
2011-10-24 3:38 ` Jason Earl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='j6kuve$6et$2@dough.gmane.org' \
--to=kgold@watson.ibm.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).