From: Philip Kaludercic <philipk@posteo.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Payas Relekar <relekarpayas@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>, John Wiegley <johnw@gnu.org>
Subject: Re: Adding use-package to core
Date: Sat, 12 Nov 2022 15:46:28 +0000 [thread overview]
Message-ID: <87mt8wxjjf.fsf@posteo.net> (raw)
In-Reply-To: <CADwFkmmEiLY71a1t2em_xXVkz+7TwxwYtkWL3Jxpc06-7wN_BQ@mail.gmail.com> (Stefan Kangas's message of "Sat, 12 Nov 2022 07:38:23 -0800")
Stefan Kangas <stefankangas@gmail.com> writes:
> Philip Kaludercic <philipk@posteo.net> writes:
>
>> I cannot evaluate this, but isn't use-package a relatively stable
>> package, that is mostly being bug-fixed? There really aren't that many
>> new features being added all the time, so this might not be that
>> important. Or am I mistaken?
>
> I don't think you're wrong, however I don't see any clear benefits to
> making it a :core package as compared to just adding it as a normal
> package, as long as it's developed externally. It's less work, and
> seems to be good enough for org-mode, for example.
>
> But you're right that it might not be that important. Either or works.
I just checked elpa-packages, assuming that the modus-themes were
externally synchronised, but apparently this isn't the case. Maybe we
could take a look at discussion from when Modus was merged into the core,
to find arguments pro and contra.
>> No, we have recently decided to scrap that documentation source in
>> favour of the documentation generated on elpa.gnu.org -- that is if I
>> understood everything correctly.
>
> OK, thanks. I now did my homework and read the related threads (sorry
> for not doing that first).
No problem.
> 1. Does that mean that it is actually preferred to make all changes
> directly in use-package.texi now?
That is my understanding
> 2. Should use-package.org just be scrapped, then? (I guess that, if the
> answer is yes, we should first export the latest version of that file
> to use-package.texi, and then continue from there.)
That would follow.
> 3. Payas mentioned working on the texinfo sources. What's the status of
> that work? I'm ready to get started, but it seems better if we can
> avoid doing the same work twice, so maybe I should base it on his
> latest version?
That I cannot say.
>> How does Org-mode distinguish between @key, @kbd, @code and @var?
>
> See org-setup.org, org.org and the generated file org.texi. Basically
> they use org-mode macros to add texinfo markup.
Oh, that is interesting. Perhaps this would work too, my experience
with org->texi has been dissatisfactory but limited.
next prev parent reply other threads:[~2022-11-12 15:46 UTC|newest]
Thread overview: 118+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 12:06 [ELPA] New package: use-package Payas Relekar
2022-10-25 14:14 ` Philip Kaludercic
2022-10-25 14:34 ` Payas Relekar
2022-10-25 16:09 ` Philip Kaludercic
2022-10-26 19:57 ` John Wiegley
2022-10-27 3:46 ` Payas Relekar
2022-10-27 5:25 ` Payas Relekar
[not found] ` <jwv35b92ohk.fsf-monnier+emacs@gnu.org>
[not found] ` <87v8o52mkn.fsf@gmail.com>
[not found] ` <87v8o5w2c1.fsf@posteo.net>
[not found] ` <jwvfsf9qbe4.fsf-monnier+emacs@gnu.org>
[not found] ` <877d0kbkfm.fsf@gmail.com>
[not found] ` <jwv8rl0nmb1.fsf-monnier+emacs@gnu.org>
[not found] ` <875yg4144y.fsf@gmail.com>
[not found] ` <jwvczablieq.fsf-monnier+emacs@gnu.org>
[not found] ` <87o7tv16xc.fsf@posteo.net>
[not found] ` <jwvmt9eitgd.fsf-monnier+emacs@gnu.org>
[not found] ` <87wn8i36v6.fsf@gmail.com>
[not found] ` <jwva65eef2q.fsf-monnier+emacs@gnu.org>
[not found] ` <871qqqpabk.fsf@posteo.net>
2022-10-30 4:13 ` Payas Relekar
[not found] ` <87h6zmj451.fsf@gmail.com>
[not found] ` <5EE58F68-8B9E-4DE6-BA20-3A88FFDA6528@posteo.net>
[not found] ` <jwvh6zmit8b.fsf-monnier+emacs@gnu.org>
[not found] ` <87sfj636pd.fsf@gmail.com>
[not found] ` <jwv4jvmeewq.fsf-monnier+emacs@gnu.org>
2022-10-29 17:23 ` Payas Relekar
2022-10-29 17:35 ` Stefan Monnier
[not found] ` <871qqkjwjj.fsf@gmail.com>
2022-11-03 8:06 ` Payas Relekar
[not found] ` <jwvr0ykw2ac.fsf-monnier+emacs@gnu.org>
2022-11-03 16:42 ` Payas Relekar
2022-11-03 16:57 ` Philip Kaludercic
2022-11-03 16:59 ` Payas Relekar
2022-11-03 17:15 ` Philip Kaludercic
2022-11-04 18:24 ` John Wiegley
2022-11-04 22:03 ` Philip Kaludercic
2022-11-05 8:06 ` Payas Relekar
2022-11-05 8:33 ` Philip Kaludercic
2022-11-05 8:45 ` Payas Relekar
2022-11-05 9:37 ` Philip Kaludercic
2022-11-05 10:13 ` Payas Relekar
2022-11-05 10:36 ` Philip Kaludercic
2022-11-05 11:29 ` Payas Relekar
2022-11-05 11:36 ` Philip Kaludercic
2022-11-12 5:42 ` Adding use-package to core Stefan Kangas
2022-11-12 7:25 ` Philip Kaludercic
2022-11-12 10:17 ` Stefan Kangas
2022-11-12 14:04 ` Philip Kaludercic
2022-11-12 15:38 ` Stefan Kangas
2022-11-12 15:46 ` Philip Kaludercic [this message]
2022-11-12 15:53 ` Payas Relekar
2022-11-12 16:33 ` Philip Kaludercic
2022-11-13 4:43 ` John Wiegley
2022-11-13 5:25 ` Stefan Kangas
2022-11-13 7:07 ` Philip Kaludercic
2022-11-13 7:31 ` Eli Zaretskii
2022-11-13 14:09 ` Stefan Kangas
2022-11-13 15:22 ` Philip Kaludercic
2022-11-13 15:42 ` Stefan Kangas
2022-11-15 17:25 ` Philip Kaludercic
2022-11-16 4:17 ` Stefan Kangas
2022-11-16 7:59 ` Philip Kaludercic
2022-11-03 17:22 ` [ELPA] New package: use-package Stefan Monnier
2022-10-25 15:37 ` Stefan Monnier
2022-10-25 15:45 ` Payas Relekar
2022-10-25 16:50 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2022-11-13 7:14 Adding use-package to core Payas Relekar
2022-11-13 11:55 Payas Relekar
2022-11-13 17:31 ` xenodasein--- via Emacs development discussions.
2022-11-13 17:40 ` Philip Kaludercic
2022-11-13 18:05 ` Stefan Kangas
2022-11-13 18:42 ` xenodasein--- via Emacs development discussions.
2022-11-13 18:24 ` John Wiegley
2022-11-13 16:11 xenodasein--- via Emacs development discussions.
2022-11-13 16:48 ` Eli Zaretskii
2022-11-13 17:53 ` John Wiegley
2022-11-13 18:13 ` Eli Zaretskii
2022-11-13 18:45 ` John Wiegley
2022-11-13 18:05 ` Stefan Kangas
[not found] ` <838rkels13.fsf@gnu.org-NGltIw7----9>
2022-11-13 18:12 ` xenodasein--- via Emacs development discussions.
2022-11-13 18:22 ` Stefan Kangas
2022-11-13 18:31 ` Eli Zaretskii
2022-11-13 19:19 ` xenodasein--- via Emacs development discussions.
2022-11-13 20:08 ` Eli Zaretskii
2022-11-13 18:46 ` John Wiegley
2022-11-13 19:02 ` xenodasein--- via Emacs development discussions.
2022-11-13 19:48 ` John Wiegley
2022-11-13 20:04 ` Eli Zaretskii
2022-11-14 10:32 ` xenodasein--- via Emacs development discussions.
2022-11-14 13:30 ` Eli Zaretskii
2022-11-14 0:27 ` Po Lu
2022-11-14 10:12 ` xenodasein--- via Emacs development discussions.
2022-11-14 10:47 ` Po Lu
2022-11-14 11:52 ` xenodasein--- via Emacs development discussions.
2022-11-14 12:19 ` Po Lu
2022-11-15 15:39 ` Michael Albinus
2022-11-14 13:54 ` Eli Zaretskii
2022-11-14 14:47 ` xenodasein--- via Emacs development discussions.
2022-11-14 17:39 ` Eli Zaretskii
2022-11-15 15:38 ` xenodasein--- via Emacs development discussions.
2022-11-15 19:22 ` Eli Zaretskii
2022-11-18 19:29 ` Sean Whitton
2022-11-18 19:33 ` Philip Kaludercic
2022-11-18 19:42 ` Eli Zaretskii
2022-11-18 20:43 ` Philip Kaludercic
2022-11-19 7:12 ` Eli Zaretskii
2022-11-19 7:33 ` Philip Kaludercic
2022-11-19 8:04 ` Eli Zaretskii
2022-11-19 10:09 ` Philip Kaludercic
2022-11-19 10:31 ` Eli Zaretskii
2022-11-19 11:02 ` Philip Kaludercic
2022-11-19 11:15 ` Stefan Kangas
2022-11-19 11:58 ` Eli Zaretskii
2022-11-19 12:15 ` Philip Kaludercic
2022-11-19 15:28 ` Stefan Monnier
2022-11-19 15:36 ` Philip Kaludercic
2022-11-19 15:46 ` Eli Zaretskii
2022-11-19 15:26 ` Stefan Monnier
2022-11-16 8:28 Payas Relekar
2022-11-16 9:30 ` Stefan Kangas
2022-11-16 13:35 ` Eli Zaretskii
2022-11-16 14:18 Payas Relekar
2022-11-16 14:52 ` Eli Zaretskii
2022-11-16 19:35 ` John Wiegley
2022-11-16 15:29 Payas Relekar
2022-11-16 16:04 ` Philip Kaludercic
2022-11-16 16:51 ` Eli Zaretskii
2022-11-16 17:01 ` Philip Kaludercic
2022-11-16 19:29 ` Eli Zaretskii
2022-11-17 0:33 ` Stefan Kangas
2022-11-17 6:40 ` Eli Zaretskii
2022-11-17 7:17 ` Stefan Kangas
2022-11-17 7:24 ` Payas Relekar
2022-11-17 16:18 ` John Wiegley
2022-11-17 7:33 ` Eli Zaretskii
2022-11-17 7:58 ` Stefan Kangas
2022-11-18 0:32 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
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=87mt8wxjjf.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=johnw@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=relekarpayas@gmail.com \
--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 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).