unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Wiegley <johnw@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: "xenodasein@tutanota.de" <xenodasein@tutanota.de>,
	 xenodasein--- viaEmacs development discussions.
	<emacs-devel@gnu.org>,  Eli Zaretskii <eliz@gnu.org>,
	 "stefankangas@gmail.com" <stefankangas@gmail.com>
Subject: Re: [External] : Re: Adding use-package to core
Date: Sun, 13 Nov 2022 22:02:03 -0800	[thread overview]
Message-ID: <m235amhy5g.fsf@newartisans.com> (raw)
In-Reply-To: <SJ0PR10MB5488DB1734C89EA26E378CF4F3029@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Sun, 13 Nov 2022 22:03:03 +0000")

>>>>> Drew Adams <drew.adams@oracle.com> writes:

> 1. "Customization beyond what Customize provides"

> What kinds of such customization, besides the one you call out next (#2)?

Defining custom functions, binding keys, advising functions, adding functions
onto hooks (when the hook isn't customizable), using `setq` when necessary,
etc.

use-package was originally created to eliminate repeated boilerplate in my
init.el file, because, not only do I want all of these customizations, but I
want them to load FAST and come into play only if I actually use the package.

> 2. "allows you to concentrate changes related to the same package in one
> place"

> Can you be more specific here? How does what you have in mind differ from
> what customize groups provide?

Customize group is great, but it only works for what is customizable.

I'm a huge fan of customize, btw, and have been using it for many years. The
fact that my init.el is 4.6k lines long should tell you that it doesn't
satisfy all my needs; 463 use-package declarations are needed to achieve that.

  https://github.com/jwiegley/dot-emacs/blob/master/init.el

-- 
John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2



  parent reply	other threads:[~2022-11-14  6:02 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-13 16:11 Adding use-package to core 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 22:03           ` [External] : " Drew Adams
2022-11-13 22:45             ` North Year
2022-11-13 23:13             ` Matthew Carter
2022-11-14  8:10               ` Juanma Barranquero
2022-11-14  4:17             ` Tim Cross
2022-11-14  6:02             ` John Wiegley [this message]
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 16:24                 ` Configuration helpers (wad: Adding use-package to core) Stefan Monnier
2022-11-15 19:22                 ` Adding use-package to core Eli Zaretskii
2022-11-18 19:29   ` Sean Whitton
2022-11-18 19:33     ` Philip Kaludercic
2022-11-18 19:48       ` [External] : " Drew Adams
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

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=m235amhy5g.fsf@newartisans.com \
    --to=johnw@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stefankangas@gmail.com \
    --cc=xenodasein@tutanota.de \
    /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).