all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Juri Linkov <juri@jurta.org>
Cc: Drew Adams <drew.adams@oracle.com>,
	joakim@verona.se,
	Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: Should Emacs have an upgrade procedure?
Date: Mon, 22 Mar 2010 02:32:13 +0100	[thread overview]
Message-ID: <e01d8a51003211832q7bff8f56m283a477f817afb11@mail.gmail.com> (raw)
In-Reply-To: <87y6hlw3un.fsf@mail.jurta.org>

On Mon, Mar 22, 2010 at 2:18 AM, Juri Linkov <juri@jurta.org> wrote:
>>> I think this could be better done with the Customization UI.
>>
>> Yes, but a special customization buffer with the relevant options and
>> with new/old settings button too.
>
> What I meant is the existing command `customize-changed-options'
> where you specify the version number, and it displays all settings
> that were added or redefined since that version.


Thanks, I had forgotten that.

It is very good command - but still not good enough for the purpose. I
think it needs info about what is new and what is changed and links to
explanations.




  reply	other threads:[~2010-03-22  1:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-21 16:41 Should Emacs have an upgrade procedure? joakim
2010-03-21 17:21 ` Drew Adams
2010-03-21 20:36   ` joakim
2010-03-21 23:55     ` Juri Linkov
2010-03-22  1:14       ` Lennart Borgman
2010-03-22  1:18         ` Juri Linkov
2010-03-22  1:32           ` Lennart Borgman [this message]
2010-03-21 18:55 ` Ted Zlatanov
2010-03-21 19:34   ` joakim
2010-03-21 20:39   ` Lennart Borgman
2010-03-21 22:49     ` Ted Zlatanov
2010-03-21 22:53       ` Lennart Borgman
2010-03-22  1:32         ` Ted Zlatanov
2010-03-22  1:36           ` Lennart Borgman
2010-03-22  2:25             ` Ted Zlatanov
2010-03-22 13:19               ` Ted Zlatanov
2010-03-22  2:07 ` Stefan Monnier

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=e01d8a51003211832q7bff8f56m283a477f817afb11@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=joakim@verona.se \
    --cc=juri@jurta.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.
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.