From: joakim@verona.se
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: Should Emacs have an upgrade procedure?
Date: Sun, 21 Mar 2010 20:34:29 +0100 [thread overview]
Message-ID: <m339zteaey.fsf@verona.se> (raw)
In-Reply-To: <87eijd7be3.fsf@lifelogs.com> (Ted Zlatanov's message of "Sun, 21 Mar 2010 13:55:16 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Sun, 21 Mar 2010 17:41:52 +0100 joakim@verona.se wrote:
>
> j> Should Emacs have an upgrade procedure?
> j> Here's a user story:
>
> j> - The user has just installed Emacs 24, previously having running
> j> Emacs23
> j> - The Emacs splash screen shows a message: "A number of defaults have
> j> been changed between Emacs 23 and 24. Would you like to go through the
> j> changes, or just enable them?". This message is NOT shown if the user
> j> previously had expressed an opinion about these particular defaults.
>
> I think assistant.el (in Gnus) could be used to automate this.
>
> j> OK, you get the picture I suppose. Good or bad? There are elisp
> j> libraries out there that already implements this of course.
>
> Any specifics? I didn't know of such libraries.
I just remembered having seen something. Maybe it was in ECB, maybe in
Gnus. Not sure.
>
> Ted
>
>
--
Joakim Verona
next prev parent reply other threads:[~2010-03-21 19:34 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
2010-03-21 18:55 ` Ted Zlatanov
2010-03-21 19:34 ` joakim [this message]
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
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=m339zteaey.fsf@verona.se \
--to=joakim@verona.se \
--cc=emacs-devel@gnu.org \
--cc=tzz@lifelogs.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).