From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, johnw@newartisans.com
Subject: Re: emacs-29 acd462b0306: ; Improve the use-package manual
Date: Sat, 10 Dec 2022 12:34:20 -0800 [thread overview]
Message-ID: <CADwFkmk_pY7sHKYAqnWoa8a0O=EaTETRF6o0-b=SoeXGTe6SUg@mail.gmail.com> (raw)
In-Reply-To: <83k02zwd0z.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> I'm saying that we should perhaps use "library" more and "package"
> less, because "package" is basically a misnomer here.
Right, then I understand what you're saying. The problem here is that
"use-package" basically tries to hide away (or abstract, if you prefer)
the fact that packages and libraries are not the same thing. Which
happens to work well 99 % of the time, but is also not a massive hurdle
for the final 1 %. It is somewhat confusing, however, perhaps even more
so if you know the full story.
That said, I very much agree that we should try to be more precise when
possible. Perhaps changing out "package" for "library" in several
places would be a good way to make things more clear.
>> I think we can drop either the window-system example or the system-type
>> example. But I don't know which one is more useful.
>
> The one where there are two values, not one, I guess?
The examples we have are:
:if (eq system-type 'gnu/linux)
and
:if (memq window-system '(ns x))
Do you mean that the `window-system' one is the more useful one?
next prev parent reply other threads:[~2022-12-10 20:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <167059642832.4265.15913417645926264658@vcs2.savannah.gnu.org>
[not found] ` <20221209143348.961DEC0E4CA@vcs2.savannah.gnu.org>
2022-12-10 11:57 ` emacs-29 acd462b0306: ; Improve the use-package manual Stefan Kangas
2022-12-10 14:26 ` Eli Zaretskii
2022-12-10 20:34 ` Stefan Kangas [this message]
2022-12-11 6:22 ` Eli Zaretskii
2022-12-11 14:24 ` Stefan Monnier
2022-12-11 20:04 ` John Yates
2022-12-12 1:35 ` Stefan Kangas
2022-12-12 1:34 ` Stefan Kangas
2022-12-10 16:20 ` Stefan Monnier
2022-12-10 16:30 ` Philip Kaludercic
2022-12-10 16:40 ` Stefan Monnier
2022-12-12 19:37 ` John Wiegley
2022-12-12 20:06 ` Philip Kaludercic
2022-12-10 20:33 ` Stefan Kangas
2022-12-10 22:01 ` Stefan Monnier
2022-12-11 7:09 ` Eli Zaretskii
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='CADwFkmk_pY7sHKYAqnWoa8a0O=EaTETRF6o0-b=SoeXGTe6SUg@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=johnw@newartisans.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 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).