unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: David Masterson <dsmasterson@gmail.com>
Cc: Richard Stallman <rms@gnu.org>, emacs-devel@gnu.org
Subject: Re: use-package documentation
Date: Fri, 06 Jan 2023 07:06:42 +0000	[thread overview]
Message-ID: <87fscodtvh.fsf@localhost> (raw)
In-Reply-To: <SJ0PR03MB545574B53ABA0D5EC786C2F2A2FB9@SJ0PR03MB5455.namprd03.prod.outlook.com>

David Masterson <dsmasterson@gmail.com> writes:

> Question: is it too early to "integrate" use-package documentation in
> standard Emacs documents when there are other variants of use-package
> (quelpa, straight, etc.) out there that may enhance or replace it?

quelpa and straight are completely different packages solving completely
different set of problems. They just _integrate_ with use-package.

use-package is for configuration. quelpa and straight are alternatives
to package.el

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>



  reply	other threads:[~2023-01-06  7:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30  4:03 use-package documentation Richard Stallman
2022-12-30  9:01 ` Eli Zaretskii
2022-12-31 11:28   ` Stefan Kangas
2023-01-01  8:39     ` Eli Zaretskii
2023-01-01  3:04   ` Richard Stallman
2023-01-01  6:46     ` Eli Zaretskii
2023-01-04 19:23       ` John Wiegley
2023-01-05 10:36         ` Stefan Kangas
2023-01-05 11:19           ` Eli Zaretskii
2023-01-06  4:37         ` Richard Stallman
2023-01-06  7:13           ` Eli Zaretskii
2022-12-30  9:02 ` Philip Kaludercic
2023-01-06  6:03 ` David Masterson
2023-01-06  7:06   ` Ihor Radchenko [this message]
2023-01-06  7:43   ` 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=87fscodtvh.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=dsmasterson@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.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).