From: Aaron Ecay <aaronecay@gmail.com>
To: chrisdone@googlemail.com, emacs-devel@gnu.org
Subject: Re: Support for bringing package change logs to the user's attention
Date: Fri, 25 May 2018 15:31:42 +0100 [thread overview]
Message-ID: <87a7sn7qnl.fsf@gmail.com> (raw)
In-Reply-To: <CAAJHNPAY9VFAzorvFfBh1vuJcmyY9B=10x8o3G56a9neue=Tdg@mail.gmail.com>
Hi Chris,
2018ko maiatzak 25an, Christopher Done-ek idatzi zuen:
[...]
> I would like that there be explicit support for:
>
> A. When I load an Emacs package that is newer than last time, that Emacs
> automatically brings up to my attention a buffer with "what's new" in
> the package.
Itʼs not automatic, but the ‘customize-changed’ function displays the
user customization options that have been added or changed between some
(specified) past version of emacs and the running version.
The drawbacks are:
- You just see a buffer full of options, not a narrative like a NEWS
file that groups changes logically and/or in order of importance.
- It only works for emacs core, not packages (but bug#31383 is a request
to change that).
- As mentioned it is not automatic (though Iʼm sure that there are
people for whom an automated change announcement itself would be
considered a drawback...).
Just FYI...
--
Aaron Ecay
next prev parent reply other threads:[~2018-05-25 14:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 11:47 Support for bringing package change logs to the user's attention Christopher Done
2018-05-25 11:50 ` Christopher Done
2018-05-25 14:26 ` Drew Adams
2018-05-25 14:31 ` Aaron Ecay [this message]
2018-05-25 16:40 ` Eric Abrahamsen
2018-05-25 17:16 ` Noam Postavsky
2018-05-25 17:51 ` Eric Abrahamsen
2018-05-26 21:07 ` Stefan Monnier
2018-05-26 21:48 ` Eric Abrahamsen
2018-05-26 21:59 ` Stefan Monnier
2018-05-27 3:15 ` Van L
2018-05-28 20:34 ` John Wiegley
2018-06-26 17:59 ` Ted Zlatanov
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=87a7sn7qnl.fsf@gmail.com \
--to=aaronecay@gmail.com \
--cc=chrisdone@googlemail.com \
--cc=emacs-devel@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.
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.