unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: Migrating .emacs Configuration File to Newer Emacsen
Date: Mon, 08 Aug 2005 12:28:32 -0600	[thread overview]
Message-ID: <dd888i$h6o$1@sea.gmane.org> (raw)
In-Reply-To: <1122923897.42ee75795d293@www.x-mail.net>

Norbert Grün wrote:
 > Copying the .emacs file over to Cygwin's place resulted in a spate of
 > error messages during Emacs 21.2.1 startup, I'd rather expected a few
 > from file system references which are only three in two commands.
 >
 > Aye, I can fire up both and tediously browse both customisation trees
 > one by one, but I'd prefer a tool that takes the old .emacs file and
 > converts it to the new format. Perhaps in a "migrate.el(c)?" thus
 > using Emacs' power?

The problem is that .emacs can contain any Emacs Lisp form, so it's not
amenable to conversion -- except for the forms inserted by custom.

Is it possible to dump the entire customization tree, perhaps by writing
out every customizable variable (whether it was actually customized or
not)?  Doing so in an uncustomized emacs would give you a file for a
simple diff-based comparison between 2 different Emacs versions -- it
could even be included in the distribution.  Of course, someone would
have to go back and generate that file for previously released versions
of Emacs, but it might be a worthwhile exercise.  If the differences
between 2 Emacs versions can be resolved by mapping old variable names
to new ones etc. then it should be possible to write a useful version of
migrate.el

-- 
Kevin Rodgers

      parent reply	other threads:[~2005-08-08 18:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-01 20:18 Migrating .emacs Configuration File to Newer Emacsen Norbert Grün
2005-08-06 18:36 ` Richard M. Stallman
2005-08-06 20:04   ` Juanma Barranquero
2005-08-08 12:08     ` Richard M. Stallman
2005-08-08 13:06       ` Juanma Barranquero
2005-08-09 15:19         ` Richard M. Stallman
2005-08-09 15:39           ` Juanma Barranquero
2005-08-08 18:28 ` Kevin Rodgers [this message]

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='dd888i$h6o$1@sea.gmane.org' \
    --to=ihs_4664@yahoo.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).