unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Jean-Christophe Helary <lists@traduction-libre.org>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: package.el, a bug ? and a UX issue ?
Date: Fri, 20 Aug 2021 22:57:34 +0200	[thread overview]
Message-ID: <CADwFkm=da1pXhgyPyceZPEtRvy0ydwXacxZMgMO4aPrtjmFnew@mail.gmail.com> (raw)
In-Reply-To: <5A4457DF-91A4-4BBA-941C-3D53907C6729@traduction-libre.org>

Jean-Christophe Helary <lists@traduction-libre.org> writes:

> 1) after filtering on marked packages, clearing the filter removes the marks
>
> After packages-list is updated, using U marks the packages that can be upgraded and a message that looks like this is displayed:
>
> Packages marked for upgrading: 5
>
> When I filter the list with package-menu-filter-marked (/ m) I get the marked list of packages to upgrade.
>
> When I clear the filter with package-menu-clear-filter (/ /) I go back to the original list *but* all the marks for upgrading are gone: when I hit x expecting to be able to install the marked packages, I get "No operations specified"...

Sounds like a bug to me.

> 2) The upgrade messages are not very useful
>
> So, the number of packages to upgrade is displayed.
>
> This comes from package-menu--mark-upgrades-1 which has:
>
> (message "Packages marked for upgrading: %d" (length upgrades))
>
> "upgrades" contains a list of new packages including their new version number, but we only have the length of it.
>
> If I hit X now, I have the list of old packages with their old version number and a "upgrade y or n" message that does not leave much room for details. The old version number
>
> So, I'm wondering if it would not be a better user experience to have the U command above directly display the list of packages with package-menu-filter-marked instead ?
>
> That way, the user can still directly use X to proceed, or eventually go back to the package list and add packages (that's, if the issue 1 above did not exist).

Makes sense to me.  I'm not sure if we could do better than
package-menu-filter-marked, but perhaps that could be good for a
start.

> Are the two points above reasonable issues to work on ?

I think so, yes.  Both sound like pretty obvious improvements, so
patches would be welcome.



  reply	other threads:[~2021-08-20 20:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20 14:29 package.el, a bug ? and a UX issue ? Jean-Christophe Helary
2021-08-20 20:57 ` Stefan Kangas [this message]
2021-08-20 23:55   ` Jean-Christophe Helary
2021-08-23 12:33     ` Stefan Kangas
2021-08-23 13:11       ` Jean-Christophe Helary

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='CADwFkm=da1pXhgyPyceZPEtRvy0ydwXacxZMgMO4aPrtjmFnew@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=emacs-devel@gnu.org \
    --cc=lists@traduction-libre.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 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).