unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Corwin Brust <corwin@bru.st>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 53885@debbugs.gnu.org
Subject: bug#53885: 28.0.51 [PATCH] Autoload package-installed-p
Date: Thu, 10 Feb 2022 02:49:06 -0600	[thread overview]
Message-ID: <CAJf-WoQb=F_2Kz+Wxpn=_wD98QxK8=+X5TMxiKbKA97FprvVow@mail.gmail.com> (raw)
In-Reply-To: <877da39kqj.fsf@gnus.org>

On Thu, Feb 10, 2022 at 2:41 AM Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> Corwin Brust <corwin@bru.st> writes:
>
> > I would like to have my init scripts automatically install a package
> > that isn't available "out of the box", but only if that feature hasn't
> > already been installed.
> >
> > As things presently stand, `package-installed-p' is nearly perfect for
> > this, however one must take care to ensure package.el has been
> > manually loaded before calling it, in order to avoid Emacs raising the
> > error shown in the original report.
>
> Oh, I see -- this has nothing to do with use-package, and you could have
> used some other package manager.  You just want to be able to check
> whether a package is installed in .emacs (without saying `require
> 'package') which seems reasonable to me.

Thanks much.

I've been struggling to reply to Ell's last succinctly, but maybe your
response has helped clarify and thus saved me from that.

Eli, please let me know if you have further what/why questions, otherwise

>
> However, this comes firmly under "new functionality" and not "bug fix",
> so I'm not sure we should put it in emacs-28 at this point, no matter
> how innocuous it looks like.  But if Eli thinks otherwise, I won't
> object.

Fine by me either way.





  reply	other threads:[~2022-02-10  8:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 23:55 bug#53885: Autoload package-installed-p Corwin Brust
2022-02-09  0:05 ` bug#53885: 28.0.51 [PATCH] " Corwin Brust
2022-02-09 13:37   ` Eli Zaretskii
2022-02-09 20:16     ` Lars Ingebrigtsen
2022-02-09 23:58       ` Corwin Brust
2022-02-10  6:10         ` Eli Zaretskii
2022-02-10  6:45           ` Lars Ingebrigtsen
2022-02-10  7:21             ` Corwin Brust
2022-02-10  7:57               ` Eli Zaretskii
2022-02-10  8:09                 ` Corwin Brust
2022-02-10  8:18                   ` Eli Zaretskii
2022-02-10  8:41               ` Lars Ingebrigtsen
2022-02-10  8:49                 ` Corwin Brust [this message]
2022-02-10 12:04                 ` Eli Zaretskii
2022-02-10 14:54                   ` Corwin Brust
2022-02-10 17:29                     ` Eli Zaretskii
2022-02-09  5:39 ` bug#53885: " Corwin Brust
2022-02-09 14:39   ` Augusto Stoffel
2022-02-09 15:39     ` Corwin Brust
2022-02-10  8:42       ` Augusto Stoffel
2022-02-10  8:59         ` Philip Kaludercic
2022-02-10  9:28           ` Augusto Stoffel
2022-02-10  9:23         ` Corwin Brust
2022-02-10  9:30           ` Augusto Stoffel

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='CAJf-WoQb=F_2Kz+Wxpn=_wD98QxK8=+X5TMxiKbKA97FprvVow@mail.gmail.com' \
    --to=corwin@bru.st \
    --cc=53885@debbugs.gnu.org \
    --cc=larsi@gnus.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).