From: Ruijie Yu via "Emacs development discussions." <emacs-devel@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-29 09d6070e56e: ; Improve and update documentation of built-in package upgrades
Date: Fri, 12 May 2023 22:09:19 +0800 [thread overview]
Message-ID: <sdvo7mp7ib4.fsf@netyu.xyz> (raw)
In-Reply-To: <20230512123358.9ECA4C21705@vcs2.savannah.gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> branch: emacs-29
> commit 09d6070e56ea21a5e9720bc619c439c09e5b2680
> Author: Eli Zaretskii <eliz@gnu.org>
> Commit: Eli Zaretskii <eliz@gnu.org>
>
> ; Improve and update documentation of built-in package upgrades
>
> * doc/emacs/package.texi (Package Statuses, Package Menu)
> (Package Installation):
> * etc/NEWS: Document the options and caveats of upgrading built-in
> packages.
> ---
> doc/emacs/package.texi | 50 +++++++++++++++++++++++++++++++++++++++++++++++---
> etc/NEWS | 7 +++++++
> 2 files changed, 54 insertions(+), 3 deletions(-)
> [...]
> +In addition, when this option is non-nil, built-in packages for which
> +a new version is available in archives can be upgraded via the package
> +menu produced by 'M-x list-packages'. If you do set this option
> +non-nil, we recommend not to use the 'U' command, but instead to use
> +'/ u' to show the packages which can be upgraded, and then unmark the
> +built-in packages which you don't need to overwrite from the archives.
> [...]
When you run `/ u' on the package list buffer, you don't automatically
mark anything for upgrading, so saying "unmark" out-of-the-blue is a bit
strange to me.
For reference, you "mark" upgrades by `U', and then "execute" all queued
actions (upgrades, installs, deletions, etc) by `x'. `/ u' filters the
list of packages to only those which are upgradable, and nothing else.
Maybe we should say one of the following proof-of-concept changes?
... we recommend not to execute the 'x' command immediately after
the 'U' command, but instead ....
... but instead to use '/ u' to show the packages which can be
upgraded, and then mark the built-in packages which you are okay
with upgrading from the archives.
... but instead to use '/ u' to show the packages which can be
upgraded, then 'U' to mark all all upgradable packages, and then
unmark the built-in packages which you don't need to overwrite ....
Hope this helps.
--
Best,
RY
next parent reply other threads:[~2023-05-12 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <168389483830.11157.3184734522033933329@vcs2.savannah.gnu.org>
[not found] ` <20230512123358.9ECA4C21705@vcs2.savannah.gnu.org>
2023-05-12 14:09 ` Ruijie Yu via Emacs development discussions. [this message]
2023-05-12 14:43 ` emacs-29 09d6070e56e: ; Improve and update documentation of built-in package upgrades Eli Zaretskii
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=sdvo7mp7ib4.fsf@netyu.xyz \
--to=emacs-devel@gnu.org \
--cc=eliz@gnu.org \
--cc=ruijie@netyu.xyz \
/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.