all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-devel@gnu.org,  John Wiegley <johnw@gnu.org>
Subject: Re: use-package has been merged into emacs-29
Date: Mon, 12 Dec 2022 20:21:16 +0000	[thread overview]
Message-ID: <87o7s8s79f.fsf@posteo.net> (raw)
In-Reply-To: <CADwFkmmUVPySJHgOuBoRnCWd=0t+GtHqJ+4U1uS4cG-T7Bdp6Q@mail.gmail.com> (Stefan Kangas's message of "Sun, 11 Dec 2022 17:19:25 -0800")

Stefan Kangas <stefankangas@gmail.com> writes:

> Philip Kaludercic <philipk@posteo.net> writes:
>
>> That does make sense, but I believe to have had found instances where
>> this was not the case.  I'll try and see if I can locate those again.
>
> That will be appreciated, thanks.

I have taken a look again, and it appears I was mistaken.  That being
said, there are still a few places where I think it is not clear if
talking about the macro or the package would be correct.  E.g. compare
these two excerpts that refer to use package and a keyword:

                                                  With use-package, you
  can simplify this using the @code{:bind} keyword, as described in this
  section.

and

  @code{use-package} supports this with a @code{:map} modifier,
  taking the local keymap to bind to:

Both readings make sense, but the manual is talking about two different
things (to be fair: with a major overlap).

>> Also, this ties into the other point about the usage of @file.
>> Shouldn't the first case be wrapped in @file?
>
> I don't think we do that elsewhere, do we?  See e.g. eshell.texi or
> eglot.texi.
>
> My understanding is that it's "use-package" when referring to the
> package as a whole, "@file{use-package}" when referring to the library
> (i.e. use-package.el), and "@code{use-package}" when referring to the
> macro by that name.

Nevermind this, I see that there is only a single instance of
"@file{use-package}" left now, and it makes sense (it refers to the file
being loaded).



  reply	other threads:[~2022-12-12 20:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08 18:59 use-package has been merged into emacs-29 Stefan Kangas
2022-12-08 22:17 ` John Wiegley
2022-12-09 16:09 ` Philip Kaludercic
2022-12-09 16:18   ` Eli Zaretskii
2022-12-09 17:06     ` Philip Kaludercic
2022-12-09 19:00       ` Eli Zaretskii
2022-12-09 16:23   ` Eli Zaretskii
2022-12-09 16:26   ` Eli Zaretskii
2022-12-10 20:34   ` Stefan Kangas
2022-12-11  6:25     ` Eli Zaretskii
2022-12-12  1:19       ` Stefan Kangas
2022-12-12  3:36         ` Eli Zaretskii
2022-12-12  4:25           ` Stefan Kangas
2022-12-11 22:11     ` Philip Kaludercic
2022-12-12  1:19       ` Stefan Kangas
2022-12-12 20:21         ` Philip Kaludercic [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-09  2:11 Payas Relekar

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=87o7s8s79f.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=johnw@gnu.org \
    --cc=stefankangas@gmail.com \
    /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.