daniel/emacs
1
2
Fork 0
Code Issues 7 Pull Requests Projects Releases Wiki Activity

update packages

Browse Source
This commit is contained in:
Daniel Weschke
2025-03-11 21:14:26 +01:00
parent 45d49daef0
commit 14dcaaddde
440 changed files with 13229 additions and 8718 deletions
Download Patch File Download Diff File Expand all files Collapse all files

278
lisp/use-package/use-package.info
View File

@@ -1,4 +1,4 @@
This is use-package.info, produced by makeinfo version 6.8 from
This is use-package.info, produced by makeinfo version 7.1.1 from
use-package.texi.
This manual is for use-package, a configuration macro for simplifying
@@ -10,12 +10,12 @@ your init file.
document under the terms of the GNU Free Documentation License,
Version 1.3 or any later version published by the Free Software
Foundation; with no Invariant Sections, with the Front-Cover Texts
being “A GNU Manual”, and with the Back-Cover Texts as in (a)
being "A GNU Manual", and with the Back-Cover Texts as in (a)
below. A copy of the license is included in the section entitled
“GNU Free Documentation License”.
"GNU Free Documentation License".
(a) The FSF’s Back-Cover Text is: “You have the freedom to copy and
modify this GNU manual.”
(a) The FSF's Back-Cover Text is: "You have the freedom to copy and
modify this GNU manual."
INFO-DIR-SECTION Emacs misc features
START-INFO-DIR-ENTRY
* use-package: (use-package). Declarative package configuration for Emacs.
@@ -49,12 +49,12 @@ your init file.
document under the terms of the GNU Free Documentation License,
Version 1.3 or any later version published by the Free Software
Foundation; with no Invariant Sections, with the Front-Cover Texts
being “A GNU Manual”, and with the Back-Cover Texts as in (a)
being "A GNU Manual", and with the Back-Cover Texts as in (a)
below. A copy of the license is included in the section entitled
“GNU Free Documentation License”.
"GNU Free Documentation License".
(a) The FSF’s Back-Cover Text is: “You have the freedom to copy and
modify this GNU manual.”
(a) The FSF's Back-Cover Text is: "You have the freedom to copy and
modify this GNU manual."
* Menu:
@@ -64,7 +64,7 @@ your init file.
* Configuring Packages:: Package configuration keywords.
* Installing packages:: Ensuring packages are available.
* Byte-compiling:: Byte-compiling your init file.
* Troubleshooting:: What to do when there’s trouble.
* Troubleshooting:: What to do when there's trouble.
Appendices
* Keyword extensions:: Adding new use-package keywords.
@@ -97,7 +97,7 @@ reasons may help make some of those decisions clearer:
package raising the error, and as little else as possible, leaving
as close to a functional Emacs as possible.
5. To allow byte-compilation of one’s init file so that any warnings
5. To allow byte-compilation of one's init file so that any warnings
or errors seen are meaningful. In this way, even if
byte-compilation is not used for speed (reason 3), it can still be
used as a sanity check.
@@ -155,7 +155,7 @@ As you might expect, you can use ‘:init’ and ‘:config’ together:
In most cases, this is not necessary or desirable, as that will slow
down Emacs startup. Instead, you should try to set things up so that
packages are only loaded when they are actually needed (autoloading).
If you have installed a package from GNU ELPA that provides it’s own
If you have installed a package from GNU ELPA that provides it's own
autoloads, it is often enough to say:
(use-package foo
@@ -221,7 +221,7 @@ Emacs start. *Note Installing packages:: for details.
* Forcing loading:: Loading packages immediately.
* Conditional loading:: Loading packages conditionally.
* Loading sequentially:: Loading packages in sequence.
* Load dependencies:: Don’t load without dependencies.
* Load dependencies:: Don't load without dependencies.
* Load path:: Using a custom ‘load-path’.
* Manual autoloads:: Setting up autoloads manually.
@@ -243,7 +243,7 @@ in your ‘load-path’, it logs a warning to the ‘*Messages*’ buffer:
(use-package foo)
Note that a “package” is different from an Emacs Lisp “library”. The
Note that a "package" is different from an Emacs Lisp "library". The
above declaration tells use-package to load the _library_ ‘foo.el’,
which the overwhelming majority of cases also resides in a _package_
named ‘foo’. But the ‘foo’ package might also contain a library named
@@ -305,7 +305,7 @@ Defer loading until idle for N seconds
--------------------------------------
You can also give a numeric argument N to ‘:defer’ to specify that a
package should be loaded (if it hasn’t already) after Emacs has been
package should be loaded (if it hasn't already) after Emacs has been
idle for N seconds. For example, use this to make use-package load
‘foo’ after 30 seconds of idle time:
@@ -316,11 +316,11 @@ When to use ‘:defer’
--------------------
When using autoloading keywords, there is no need to also use ‘:defer’.
It doesn’t hurt anything to add it in this case, perhaps for extra
It doesn't hurt anything to add it in this case, perhaps for extra
clarity, but it is redundant.
You should use ‘:defer’ to force deferred loading, in cases when
use-package isn’t creating any autoloads for you. For example, you
use-package isn't creating any autoloads for you. For example, you
might know that some other package will already do something to cause
your package to load at the appropriate time. This is usually the case
when you install a package using ‘package-install’, as packages
@@ -485,7 +485,7 @@ File: use-package.info, Node: Load dependencies, Next: Load path, Prev: Loadi
While the ‘:after’ keyword delays loading until the dependencies are
loaded, the somewhat simpler ‘:requires’ keyword _never_ loads the
package if the dependencies are not available when the ‘use-package’
declaration is evaluated. In this context, “available” means that ‘foo’
declaration is evaluated. In this context, "available" means that ‘foo’
is available if ‘(featurep 'foo)’ evaluates to a non-‘nil’ value. For
example:
@@ -625,7 +625,7 @@ File: use-package.info, Node: Init keyword, Next: Config keyword, Prev: Prefa
-------------------------------------------------
The ‘:init’ section is evaluated just before the package is loaded.
Note that the ‘:init’ form is run unconditionally – even if the ‘foo’
Note that the ‘:init’ form is run unconditionally - even if the ‘foo’
package happens to not exist on your system. You must therefore
remember to restrict ‘:init’ code to only what would succeed either way.
‘:init’ also always happens before package load, whether ‘:config’ has
@@ -748,7 +748,7 @@ Here is an example of using ‘:bind’ with a list of conses:
Using special keys
------------------
Inside key strings, special keys like ‘TAB’ or ‘F1’–‘F12’ have to be
Inside key strings, special keys like ‘TAB’ or ‘F1’-‘F12’ have to be
written inside angle brackets, e.g. ‘"C-<up>"’. Standalone special
keys (and some combinations) can be written in square brackets,
e.g. ‘[tab]’ instead of ‘"<tab>"’.
@@ -835,7 +835,7 @@ keymap to bind to:
The effect of this statement is to wait until ‘helm’ has loaded, and
then to bind the key ‘C-c h’ to ‘helm-execute-persistent-action’ within
Helm’s local keymap, ‘helm-command-map’.
Helm's local keymap, ‘helm-command-map’.
Multiple uses of ‘:map’ may be specified. Any binding occurring
before the first use of ‘:map’ are applied to the global keymap:
@@ -863,7 +863,7 @@ and cannot be autoloaded using the built-in ‘autoload’ function.
To handle this case, ‘use-package’ offers a special, limited variant
of ‘:bind’ called ‘:bind-keymap’. The only difference is that the
“commands” bound to by ‘:bind-keymap’ must be keymaps defined in the
"commands" bound to by ‘:bind-keymap’ must be keymaps defined in the
package, rather than command functions. This is handled behind the
scenes by generating custom code that loads the package containing the
keymap, and then re-executes your keypress after the first load, to
@@ -947,7 +947,7 @@ library to set up keybindings. It keeps track of all keybindings you
make, so that you can display them separately from the default
keybindings.
Use ‘M-x describe-personal-keybindings’ to see all keybindings you’ve
Use ‘M-x describe-personal-keybindings’ to see all keybindings you've
set using either the ‘:bind’ keyword or the ‘bind-keys’ macro.

@@ -1040,7 +1040,7 @@ be a cons cell, a list of cons cells, or a string or regexp.
configuration, exactly as it is in Emacs out-of-the-box. That mode is
enabled automatically when a file whose name matches the regexp
‘"\\.rb\\'"’ (a file with the ‘.rb’ extension), or when the first line
of the file (known as the “shebang”) matches the string ‘"ruby"’:
of the file (known as the "shebang") matches the string ‘"ruby"’:
(use-package ruby-mode
:mode "\\.rb\\'"
@@ -1153,7 +1153,7 @@ File: use-package.info, Node: Hiding minor modes, Prev: Faces, Up: Configurin
‘use-package’ supports the diminish and delight packages, both of which
make it possible remove or change minor mode strings in your mode-line.
Which one to use is up to you, but you should normally only use one or
the other – never both.(1) To use either of them, you must first
the other - never both.(1) To use either of them, you must first
install the corresponding package from GNU ELPA.
* Menu:
@@ -1176,7 +1176,7 @@ diminish is not installed, the ‘:diminish’ keyword does nothing.
First, add the following declaration to the beginning of your init
file. The optional ‘:ensure t’ makes sure the package is installed if
it isn’t already (*note Installing packages::).
it isn't already (*note Installing packages::).
(use-package diminish :ensure t)
@@ -1206,7 +1206,7 @@ delight is not installed, the ‘:delight’ keyword does nothing.
First, add the following declaration to the beginning of your init
file. The optional ‘:ensure t’ makes sure the package is installed if
it isn’t already (*note Installing packages::).
it isn't already (*note Installing packages::).
(use-package delight :ensure t)
@@ -1222,7 +1222,7 @@ mode in the ‘foo’ package:
(use-package foo
:delight)
If the mode name doesn’t match the package name with ‘-mode’
If the mode name doesn't match the package name with ‘-mode’
appended, provide a symbol instead. For example, the following hides
‘auto-revert-mode’ from the mode line:
@@ -1500,9 +1500,9 @@ see a message to indicate this loading activity in the ‘*Messages*’
buffer. The same will happen for configuration, or ‘:config’ blocks,
that take longer than 0.1 seconds to execute.
If you’d like to see a summary how many packages you’ve loaded, what
stage of initialization they’ve reached, and how much aggregate time
they’ve spent (roughly), you can customize the user option
If you'd like to see a summary how many packages you've loaded, what
stage of initialization they've reached, and how much aggregate time
they've spent (roughly), you can customize the user option
‘use-package-compute-statistics’ to a non-‘nil’ value. Then reload your
packages, normally by restarting Emacs, to make sure that use-package
can gather statistics for all your packages.
@@ -1525,13 +1525,13 @@ File: use-package.info, Node: Disabling a package, Prev: Gathering Statistics,
7.3 Disabling a package
=======================
The ‘:disabled’ keyword inhibits loading a package, and all it’s
The ‘:disabled’ keyword inhibits loading a package, and all it's
customizations. It is equivalent to commenting out or deleting the
definition.
You could use this, for example, to temporarily disable a package
that you’re having difficulties with, or to avoid loading a package that
you’re not currently using.
that you're having difficulties with, or to avoid loading a package that
you're not currently using.
This example disables the ‘foo’ package:
@@ -1575,7 +1575,7 @@ declarations.(1)
(use-package use-package-ensure-system-package)
Now you can use the ‘:ensure-system-package’ keyword. Here’s an
Now you can use the ‘:ensure-system-package’ keyword. Here's an
example usage:
(use-package foo
@@ -1609,7 +1609,7 @@ Emacs could not locate the executable ‘foocmd’.(2)
‘:ensure-system-package’ can also take a cons where its ‘cdr’ is a
string that will get called by ‘(async-shell-command)’ to install if it
isn’t found. This does not depend upon any external package.
isn't found. This does not depend upon any external package.
(use-package tern
:ensure-system-package (tern . "npm i -g tern"))
@@ -1774,7 +1774,7 @@ Appendix C GNU Free Documentation License
author and publisher a way to get credit for their work, while not
being considered responsible for modifications made by others.
This License is a kind of “copyleft”, which means that derivative
This License is a kind of "copyleft", which means that derivative
works of the document must themselves be free in the same sense.
It complements the GNU General Public License, which is a copyleft
license designed for free software.
@@ -1795,18 +1795,18 @@ Appendix C GNU Free Documentation License
be distributed under the terms of this License. Such a notice
grants a world-wide, royalty-free license, unlimited in duration,
to use that work under the conditions stated herein. The
“Document”, below, refers to any such manual or work. Any member
of the public is a licensee, and is addressed as “you”. You accept
"Document", below, refers to any such manual or work. Any member
of the public is a licensee, and is addressed as "you". You accept
the license if you copy, modify or distribute the work in a way
requiring permission under copyright law.
A “Modified Version” of the Document means any work containing the
A "Modified Version" of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
A “Secondary Section” is a named appendix or a front-matter section
A "Secondary Section" is a named appendix or a front-matter section
of the Document that deals exclusively with the relationship of the
publishers or authors of the Document to the Document’s overall
publishers or authors of the Document to the Document's overall
subject (or to related matters) and contains nothing that could
fall directly within that overall subject. (Thus, if the Document
is in part a textbook of mathematics, a Secondary Section may not
@@ -1815,7 +1815,7 @@ Appendix C GNU Free Documentation License
of legal, commercial, philosophical, ethical or political position
regarding them.
The “Invariant Sections” are certain Secondary Sections whose
The "Invariant Sections" are certain Secondary Sections whose
titles are designated, as being those of Invariant Sections, in the
notice that says that the Document is released under this License.
If a section does not fit the above definition of Secondary then it
@@ -1823,13 +1823,13 @@ Appendix C GNU Free Documentation License
contain zero Invariant Sections. If the Document does not identify
any Invariant Sections then there are none.
The “Cover Texts” are certain short passages of text that are
The "Cover Texts" are certain short passages of text that are
listed, as Front-Cover Texts or Back-Cover Texts, in the notice
that says that the Document is released under this License. A
Front-Cover Text may be at most 5 words, and a Back-Cover Text may
be at most 25 words.
A “Transparent” copy of the Document means a machine-readable copy,
A "Transparent" copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed
@@ -1841,7 +1841,7 @@ Appendix C GNU Free Documentation License
been arranged to thwart or discourage subsequent modification by
readers is not Transparent. An image format is not Transparent if
used for any substantial amount of text. A copy that is not
“Transparent” is called “Opaque”.
"Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input format,
@@ -1854,23 +1854,23 @@ Appendix C GNU Free Documentation License
the machine-generated HTML, PostScript or PDF produced by some word
processors for output purposes only.
The “Title Page” means, for a printed book, the title page itself,
The "Title Page" means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the
material this License requires to appear in the title page. For
works in formats which do not have any title page as such, “Title
Page” means the text near the most prominent appearance of the
work’s title, preceding the beginning of the body of the text.
works in formats which do not have any title page as such, "Title
Page" means the text near the most prominent appearance of the
work's title, preceding the beginning of the body of the text.
The “publisher” means any person or entity that distributes copies
The "publisher" means any person or entity that distributes copies
of the Document to the public.
A section “Entitled XYZ” means a named subunit of the Document
A section "Entitled XYZ" means a named subunit of the Document
whose title either is precisely XYZ or contains XYZ in parentheses
following text that translates XYZ in another language. (Here XYZ
stands for a specific section name mentioned below, such as
“Acknowledgements”, “Dedications”, “Endorsements”, or “History”.)
To “Preserve the Title” of such a section when you modify the
Document means that it remains a section “Entitled XYZ” according
"Acknowledgements", "Dedications", "Endorsements", or "History".)
To "Preserve the Title" of such a section when you modify the
Document means that it remains a section "Entitled XYZ" according
to this definition.
The Document may include Warranty Disclaimers next to the notice
@@ -1900,7 +1900,7 @@ Appendix C GNU Free Documentation License
If you publish printed copies (or copies in media that commonly
have printed covers) of the Document, numbering more than 100, and
the Document’s license notice requires Cover Texts, you must
the Document's license notice requires Cover Texts, you must
enclose the copies in covers that carry, clearly and legibly, all
these Cover Texts: Front-Cover Texts on the front cover, and
Back-Cover Texts on the back cover. Both covers must also clearly
@@ -1972,15 +1972,15 @@ Appendix C GNU Free Documentation License
the Addendum below.
G. Preserve in that license notice the full lists of Invariant
Sections and required Cover Texts given in the Document’s
Sections and required Cover Texts given in the Document's
license notice.
H. Include an unaltered copy of this License.
I. Preserve the section Entitled “History”, Preserve its Title,
I. Preserve the section Entitled "History", Preserve its Title,
and add to it an item stating at least the title, year, new
authors, and publisher of the Modified Version as given on the
Title Page. If there is no section Entitled “History” in the
Title Page. If there is no section Entitled "History" in the
Document, create one stating the title, year, authors, and
publisher of the Document as given on its Title Page, then add
an item describing the Modified Version as stated in the
@@ -1990,12 +1990,12 @@ Appendix C GNU Free Documentation License
for public access to a Transparent copy of the Document, and
likewise the network locations given in the Document for
previous versions it was based on. These may be placed in the
“History” section. You may omit a network location for a work
"History" section. You may omit a network location for a work
that was published at least four years before the Document
itself, or if the original publisher of the version it refers
to gives permission.
K. For any section Entitled “Acknowledgements” or “Dedications”,
K. For any section Entitled "Acknowledgements" or "Dedications",
Preserve the Title of the section, and preserve in the section
all the substance and tone of each of the contributor
acknowledgements and/or dedications given therein.
@@ -2004,11 +2004,11 @@ Appendix C GNU Free Documentation License
in their text and in their titles. Section numbers or the
equivalent are not considered part of the section titles.
M. Delete any section Entitled “Endorsements”. Such a section
M. Delete any section Entitled "Endorsements". Such a section
may not be included in the Modified Version.
N. Do not retitle any existing section to be Entitled
“Endorsements” or to conflict in title with any Invariant
"Endorsements" or to conflict in title with any Invariant
Section.
O. Preserve any Warranty Disclaimers.
@@ -2017,15 +2017,15 @@ Appendix C GNU Free Documentation License
appendices that qualify as Secondary Sections and contain no
material copied from the Document, you may at your option designate
some or all of these sections as invariant. To do this, add their
titles to the list of Invariant Sections in the Modified Version’s
titles to the list of Invariant Sections in the Modified Version's
license notice. These titles must be distinct from any other
section titles.
You may add a section Entitled “Endorsements”, provided it contains
You may add a section Entitled "Endorsements", provided it contains
nothing but endorsements of your Modified Version by various
parties—for example, statements of peer review or that the text has
been approved by an organization as the authoritative definition of
a standard.
parties--for example, statements of peer review or that the text
has been approved by an organization as the authoritative
definition of a standard.
You may add a passage of up to five words as a Front-Cover Text,
and a passage of up to 25 words as a Back-Cover Text, to the end of
@@ -2063,10 +2063,10 @@ Appendix C GNU Free Documentation License
combined work.
In the combination, you must combine any sections Entitled
“History” in the various original documents, forming one section
Entitled “History”; likewise combine any sections Entitled
“Acknowledgements”, and any sections Entitled “Dedications”. You
must delete all sections Entitled “Endorsements.”
"History" in the various original documents, forming one section
Entitled "History"; likewise combine any sections Entitled
"Acknowledgements", and any sections Entitled "Dedications". You
must delete all sections Entitled "Endorsements."
6. COLLECTIONS OF DOCUMENTS
@@ -2087,16 +2087,16 @@ Appendix C GNU Free Documentation License
A compilation of the Document or its derivatives with other
separate and independent documents or works, in or on a volume of a
storage or distribution medium, is called an “aggregate” if the
storage or distribution medium, is called an "aggregate" if the
copyright resulting from the compilation is not used to limit the
legal rights of the compilation’s users beyond what the individual
legal rights of the compilation's users beyond what the individual
works permit. When the Document is included in an aggregate, this
License does not apply to the other works in the aggregate which
are not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one half
of the entire aggregate, the Document’s Cover Texts may be placed
of the entire aggregate, the Document's Cover Texts may be placed
on covers that bracket the Document within the aggregate, or the
electronic equivalent of covers if the Document is in electronic
form. Otherwise they must appear on printed covers that bracket
@@ -2118,8 +2118,8 @@ Appendix C GNU Free Documentation License
this License or a notice or disclaimer, the original version will
prevail.
If a section in the Document is Entitled “Acknowledgements”,
“Dedications”, or “History”, the requirement (section 4) to
If a section in the Document is Entitled "Acknowledgements",
"Dedications", or "History", the requirement (section 4) to
Preserve its Title (section 1) will typically require changing the
actual title.
@@ -2160,7 +2160,7 @@ Appendix C GNU Free Documentation License
Each version of the License is given a distinguishing version
number. If the Document specifies that a particular numbered
version of this License “or any later version” applies to it, you
version of this License "or any later version" applies to it, you
have the option of following the terms and conditions either of
that specified version or of any later version that has been
published (not as a draft) by the Free Software Foundation. If the
@@ -2168,29 +2168,29 @@ Appendix C GNU Free Documentation License
choose any version ever published (not as a draft) by the Free
Software Foundation. If the Document specifies that a proxy can
decide which future versions of this License can be used, that
proxy’s public statement of acceptance of a version permanently
proxy's public statement of acceptance of a version permanently
authorizes you to choose that version for the Document.
11. RELICENSING
“Massive Multiauthor Collaboration Site” (or “MMC Site”) means any
"Massive Multiauthor Collaboration Site" (or "MMC Site") means any
World Wide Web server that publishes copyrightable works and also
provides prominent facilities for anybody to edit those works. A
public wiki that anybody can edit is an example of such a server.
A “Massive Multiauthor Collaboration” (or “MMC”) contained in the
A "Massive Multiauthor Collaboration" (or "MMC") contained in the
site means any set of copyrightable works thus published on the MMC
site.
“CC-BY-SA” means the Creative Commons Attribution-Share Alike 3.0
"CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0
license published by Creative Commons Corporation, a not-for-profit
corporation with a principal place of business in San Francisco,
California, as well as future copyleft versions of that license
published by that same organization.
“Incorporate” means to publish or republish a Document, in whole or
"Incorporate" means to publish or republish a Document, in whole or
in part, as part of another Document.
An MMC is “eligible for relicensing” if it is licensed under this
An MMC is "eligible for relicensing" if it is licensed under this
License, and if all works that were first published under this
License somewhere other than this MMC, and subsequently
incorporated in whole or in part into the MMC, (1) had no cover
@@ -2217,7 +2217,7 @@ notices just after the title page:
Free Documentation License''.
If you have Invariant Sections, Front-Cover Texts and Back-Cover
Texts, replace the “with...Texts.” line with this:
Texts, replace the "with...Texts." line with this:
with the Invariant Sections being LIST THEIR TITLES, with
the Front-Cover Texts being LIST, and with the Back-Cover Texts
@@ -2323,60 +2323,60 @@ Index

Tag Table:
Node: Top947
Node: Basic Concepts3143
Node: Getting Started4569
Node: Loading Packages7734
Node: Loading basics9243
Ref: Loading basics-Footnote-110804
Node: Deferring loading10888
Node: Forcing loading14111
Node: Conditional loading14796
Node: Loading sequentially16960
Node: Load dependencies19541
Node: Load path20522
Node: Manual autoloads21759
Node: Configuring Packages22415
Node: Lisp Configuration23174
Node: Preface keyword24038
Node: Init keyword24944
Node: Config keyword25564
Node: Best practices26289
Node: Key bindings27766
Node: Global keybindings28536
Node: Binding in keymaps32350
Node: Binding to a keymap33561
Node: Binding to repeat-maps34595
Node: Displaying keybindings36982
Node: Hooks37544
Node: Modes and interpreters40312
Node: Magic handlers41851
Node: User options42680
Node: Faces44095
Node: Hiding minor modes44892
Ref: Hiding minor modes-Footnote-145599
Node: Diminish45654
Ref: Diminish-Footnote-146593
Node: Delight46652
Ref: Delight-Footnote-148460
Node: Installing packages48524
Node: Install package49137
Node: Pinning packages49967
Ref: Pinning packages-Footnote-151661
Node: Other package managers51741
Node: Byte-compiling52613
Node: Troubleshooting54605
Node: Troubleshooting Options55956
Node: Gathering Statistics57518
Node: Disabling a package59085
Node: Keyword extensions59801
Node: use-package-ensure-system-package60289
Ref: use-package-ensure-system-package-Footnote-163298
Ref: use-package-ensure-system-package-Footnote-263566
Node: Creating an extension63697
Node: History67109
Node: GNU Free Documentation License67782
Node: Index93134
Node: Top935
Node: Basic Concepts3115
Node: Getting Started4539
Node: Loading Packages7702
Node: Loading basics9209
Ref: Loading basics-Footnote-110762
Node: Deferring loading10846
Node: Forcing loading14063
Node: Conditional loading14748
Node: Loading sequentially16912
Node: Load dependencies19493
Node: Load path20470
Node: Manual autoloads21707
Node: Configuring Packages22363
Node: Lisp Configuration23122
Node: Preface keyword23986
Node: Init keyword24892
Node: Config keyword25510
Node: Best practices26235
Node: Key bindings27712
Node: Global keybindings28482
Node: Binding in keymaps32294
Node: Binding to a keymap33503
Node: Binding to repeat-maps34533
Node: Displaying keybindings36920
Node: Hooks37480
Node: Modes and interpreters40248
Node: Magic handlers41783
Node: User options42612
Node: Faces44027
Node: Hiding minor modes44824
Ref: Hiding minor modes-Footnote-145529
Node: Diminish45584
Ref: Diminish-Footnote-146521
Node: Delight46580
Ref: Delight-Footnote-148384
Node: Installing packages48448
Node: Install package49061
Node: Pinning packages49891
Ref: Pinning packages-Footnote-151585
Node: Other package managers51665
Node: Byte-compiling52537
Node: Troubleshooting54529
Node: Troubleshooting Options55880
Node: Gathering Statistics57442
Node: Disabling a package59001
Node: Keyword extensions59711
Node: use-package-ensure-system-package60199
Ref: use-package-ensure-system-package-Footnote-163204
Ref: use-package-ensure-system-package-Footnote-263472
Node: Creating an extension63603
Node: History67015
Node: GNU Free Documentation License67688
Node: Index92839

End Tag Table