all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ruijie Yu <ruijie@netyu.xyz>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-29 09d6070e56e: ; Improve and update documentation of built-in package upgrades
Date: Fri, 12 May 2023 17:43:21 +0300	[thread overview]
Message-ID: <83wn1dbofq.fsf@gnu.org> (raw)
In-Reply-To: <sdvo7mp7ib4.fsf@netyu.xyz> (message from Ruijie Yu on Fri, 12 May 2023 22:09:19 +0800)

> From: Ruijie Yu <ruijie@netyu.xyz>
> Cc: emacs-devel@gnu.org
> Date: Fri, 12 May 2023 22:09:19 +0800
> 
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > +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.

Thanks, fixed.

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

I don't (yet) see the need for that.  I think telling people to stay
away of 'U' if they customize this new variable is good enough for
NEWS.  The manual tells more.



      reply	other threads:[~2023-05-12 14:43 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   ` emacs-29 09d6070e56e: ; Improve and update documentation of built-in package upgrades Ruijie Yu via Emacs development discussions.
2023-05-12 14:43     ` Eli Zaretskii [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83wn1dbofq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@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.