From: Jambunathan K <kjambunathan@gmail.com>
To: Perry Smith <pedzsan@gmail.com>
Cc: help-gnu-emacs List <help-gnu-emacs@gnu.org>
Subject: Re: Upgrading suggestions
Date: Tue, 04 Oct 2011 23:39:02 +0530 [thread overview]
Message-ID: <81vcs4pr29.fsf@gmail.com> (raw)
In-Reply-To: <C0729F91-44CC-4A84-B773-296A4579180D@gmail.com> (Perry Smith's message of "Tue, 4 Oct 2011 12:28:57 -0500")
The following are your friends.
C-h n
M-x customize-changed-options RET
> 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-04 18:09 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 [this message]
2011-10-04 20:32 ` S Boucher
2011-10-06 19:19 ` Ken Goldman
[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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81vcs4pr29.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=pedzsan@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.