all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Eduardo Mercovich <eduardo@mercovich.net>, 41436@debbugs.gnu.org
Subject: bug#41436: 26.1; How to list upgradable packages only
Date: Sun, 23 Aug 2020 12:43:56 -0400	[thread overview]
Message-ID: <CADwFkmmY-sEYS14BkaqjoKAFkSovd968+_n_n2_Se+f2CDKvbw@mail.gmail.com> (raw)
In-Reply-To: <878shlcrrc.fsf@biologica>

Eduardo Mercovich <eduardo@mercovich.net> writes:

> But, for my life, even after quite some searching and reading I can't
> find how to filter the list by that status (the command
> package-menu-filter does something different or I don't understand how
> to use it for this), so I can see only the packages that can be
> upgraded.

This feature is already in master and will be part of Emacs 28.1.
Unfortunately, the patch wasn't merged in time for Emacs 27.

commit aea12d4903136c057bb14d3fd7683bf7a4e1eff6
Author: Stefan Kangas <stefankangas@gmail.com>
Date:   Wed Feb 5 13:12:01 2020 +0100

    Add new filter commands to Package Menu (Bug#38424)

    * lisp/emacs-lisp/package.el (package-menu-filter-by-version)
    (package-menu-filter-by-status, package-menu-filter-by-archive):
    New filter commands.

Please try it out and see if it works for you.

Best regards,
Stefan Kangas





  parent reply	other threads:[~2020-08-23 16:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-21 14:00 bug#41436: 26.1; How to list upgradable packages only Eduardo Mercovich
2020-08-23 16:16 ` Marcin Włodarczak
2020-08-23 16:43 ` Stefan Kangas [this message]
2020-08-23 16:58   ` Marcin Włodarczak
2020-08-23 17:55     ` Stefan Kangas
2020-08-23 21:01       ` Eduardo Mercovich
2020-09-08 12:53       ` Stefan Kangas
2020-10-19 18:42         ` Stefan Kangas

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=CADwFkmmY-sEYS14BkaqjoKAFkSovd968+_n_n2_Se+f2CDKvbw@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=41436@debbugs.gnu.org \
    --cc=eduardo@mercovich.net \
    /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.