From: Philip Kaludercic <philipk@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Adam Porter <adam@alphapapa.net>, Dmitry Gutov <dmitry@gutov.dev>,
Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>,
62750@debbugs.gnu.org
Subject: bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade'
Date: Wed, 12 Apr 2023 07:35:48 +0000 [thread overview]
Message-ID: <87fs95a6y3.fsf@posteo.net> (raw)
In-Reply-To: <jwvy1myje0p.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 11 Apr 2023 17:40:05 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>>> I don't think that "update" and "upgrade" have that clear of a semantic
>>>> difference in practice to necessitate a renaming.
>>> I'd tend to agree.
>>
>> Here's an argument in favor of renaming:
>>
>> These commands use the term 'update'. But package-menu-mark-upgrades, which
>> has been in package.el for years, uses the term 'upgrade' in its name and
>> its docstring ("all upgradable packages", etc). There are a few auxiliary
>> functions which also use that term, but this is the public-facing one.
I have to admit that I didn't even notice that the command used the word
upgrade... Probably because I only invoked it using the binding, though
I do get the point with it being inconsistent.
>> So now we have divergent terminology. Which implies that there is some
>> difference between "upgrading" and "updating" in package.el, while there
>> is none.
>
> Good point.
>
> It's annoyingly late to rename, but if we rename without compatibility
> aliases (which seems to be an option since these are new in Emacs-29),
> then I'd be in favor.
What are compatibility aliases? I must have missed something?
> Stefan
next prev parent reply other threads:[~2023-04-12 7:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 12:53 bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade' Adam Porter
2023-04-10 13:18 ` Eli Zaretskii
2023-04-10 13:25 ` Philip Kaludercic
2023-04-10 14:31 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-11 21:28 ` Dmitry Gutov
2023-04-11 21:40 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-12 7:35 ` Philip Kaludercic [this message]
2023-04-12 13:22 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-12 13:28 ` Eli Zaretskii
2023-04-12 13:34 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-15 1:34 ` Dmitry Gutov
2023-04-23 23:06 ` Dmitry Gutov
2023-04-24 12:02 ` Eli Zaretskii
2023-04-24 17:28 ` Adam Porter
2023-04-24 18:54 ` Dmitry Gutov
2023-04-24 19:13 ` Eli Zaretskii
2023-04-24 19:38 ` Dmitry Gutov
2023-05-01 1:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-01 13:19 ` Dmitry Gutov
2023-04-12 13:44 ` Philip Kaludercic
2023-04-12 14:36 ` João Távora
2023-04-19 22:23 ` Jim Porter
2023-04-27 23:27 ` Dmitry Gutov
2023-04-28 14:26 ` Philip Kaludercic
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=87fs95a6y3.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=62750@debbugs.gnu.org \
--cc=adam@alphapapa.net \
--cc=dmitry@gutov.dev \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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).