diff options
| author | bh <qn+git@excalibur.computer> | 2025-12-10 17:24:50 +0800 |
|---|---|---|
| committer | bh <qn+git@excalibur.computer> | 2025-12-10 17:24:50 +0800 |
| commit | 03adcf13345cc04d3bee259239794f4c4e55610c (patch) | |
| tree | bd3dd74bb8000cccb7029f806ae254cb7169420f /straight/build | |
Initial Commit!
Diffstat (limited to 'straight/build')
99 files changed, 2279 insertions, 0 deletions
diff --git a/straight/build/annalist/annalist-autoloads.el b/straight/build/annalist/annalist-autoloads.el new file mode 100644 index 0000000..0b103cf --- /dev/null +++ b/straight/build/annalist/annalist-autoloads.el @@ -0,0 +1,45 @@ +;;; annalist-autoloads.el --- automatically extracted autoloads (do not edit) -*- lexical-binding: t -*- +;; Generated by the `loaddefs-generate' function. + +;; This file is part of GNU Emacs. + +;;; Code: + + + +;;; Generated autoloads from annalist.el + +(autoload 'annalist-record "annalist" "\ +In the store for ANNALIST, TYPE, and LOCAL, record RECORD. +ANNALIST should correspond to the package/user recording this information (e.g. +'general, 'me, etc.). TYPE is the type of information being recorded (e.g. +'keybindings). LOCAL corresponds to whether to store RECORD only for the current +buffer. This information together is used to select where RECORD should be +stored in and later retrieved from with `annalist-describe'. RECORD should be a +list of items to record and later print as org headings and column entries in a +single row. If PLIST is non-nil, RECORD should be a plist instead of an ordered +list (e.g. '(keymap org-mode-map key \"C-c a\" ...)). The plist keys should be +the symbols used for the definition of TYPE. + +(fn ANNALIST TYPE RECORD &key LOCAL PLIST)") +(autoload 'annalist-describe "annalist" "\ +Describe information recorded by ANNALIST for TYPE. +For example: (annalist-describe 'general 'keybindings) If VIEW is non-nil, use +those settings for displaying recorded information instead of the defaults. + +(fn ANNALIST TYPE &optional VIEW)") +(register-definition-prefixes "annalist" '("annalist-")) + +;;; End of scraped data + +(provide 'annalist-autoloads) + +;; Local Variables: +;; version-control: never +;; no-byte-compile: t +;; no-update-autoloads: t +;; no-native-compile: t +;; coding: utf-8-emacs-unix +;; End: + +;;; annalist-autoloads.el ends here diff --git a/straight/build/annalist/annalist.el b/straight/build/annalist/annalist.el new file mode 120000 index 0000000..3039c85 --- /dev/null +++ b/straight/build/annalist/annalist.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/annalist/annalist.el
\ No newline at end of file diff --git a/straight/build/annalist/annalist.elc b/straight/build/annalist/annalist.elc Binary files differnew file mode 100644 index 0000000..aebfd4a --- /dev/null +++ b/straight/build/annalist/annalist.elc diff --git a/straight/build/annalist/annalist.info b/straight/build/annalist/annalist.info new file mode 100644 index 0000000..8b4398a --- /dev/null +++ b/straight/build/annalist/annalist.info @@ -0,0 +1,545 @@ +This is annalist.info, produced by makeinfo version 7.2 from +annalist.texi. + +INFO-DIR-SECTION Emacs +START-INFO-DIR-ENTRY +* Annalist: (annalist). Record and display information such as keybindings. +END-INFO-DIR-ENTRY + + +File: annalist.info, Node: Top, Next: Usage, Up: (dir) + +Annalist User Manual +******************** + +file:https://melpa.org/packages/annalist-badge.svg +(https://melpa.org/#/annalist) +https://travis-ci.org/noctuid/annalist.el.svg?branch=master +(https://travis-ci.org/noctuid/annalist.el) + + Incessant wind sweeps the plain. It murmurs on across grey stone, + carrying dust from far climes to nibble eternally at the memorial + pillars. There are a few shadows out there still but they are the + weak and the timid and the hopelessly lost. + + It is immortality of a sort. + + Memory is immortality of a sort. + + In the night, when the wind dies and silence rules the place of + glittering stone, I remember. And they all live again. + + ‘annalist.el’ is a library that can be used to record information and +later print that information using ‘org-mode’ headings and tables. It +allows defining different types of things that can be recorded (e.g. +keybindings, settings, hooks, and advice) and supports custom filtering, +sorting, and formatting. ‘annalist’ is primarily intended for use in +other packages like ‘general’ and ‘evil-collection’, but it can also be +used directly in a user's configuration. + +[https://user-images.githubusercontent.com/4250696/63480582-64e2cb00-c460-11e9-9571-706b5b96992c] + +* Menu: + +* Usage:: + +-- The Detailed Node Listing -- + +Usage + +* Disabling Annalist:: +* Terminology:: +* Settings:: +* Defining New Types:: +* Defining Views:: +* Recording:: +* Describing:: +* Helper Functions:: +* Builtin Types:: + +Defining New Types + +* Type Top-level Settings:: +* Type Item Settings:: +* ‘:record-update’, ‘:preprocess’, and ‘:postprocess’ Settings Argument: record-update preprocess and postprocess Settings Argument. + +Defining Views + +* View Top-level Settings:: +* View Item Settings:: + +Helper Functions + +* List Helpers:: +* Formatting Helpers:: +* Sorting Helpers:: + +Builtin Types + +* Keybindings Type:: + + +File: annalist.info, Node: Usage, Prev: Top, Up: Top + +1 Usage +******* + +* Menu: + +* Disabling Annalist:: +* Terminology:: +* Settings:: +* Defining New Types:: +* Defining Views:: +* Recording:: +* Describing:: +* Helper Functions:: +* Builtin Types:: + + +File: annalist.info, Node: Disabling Annalist, Next: Terminology, Up: Usage + +1.1 Disabling Annalist +====================== + + What fool always has his nose in everywhere because he thinks he + has to know so he can record it in his precious Annals? + + If you use a library that uses ‘annalist’ (e.g. ‘evil-collection’ or +‘general’) but don't need it's functionality during init or at all, you +can set ‘annalist-record’ to nil to shave some milliseconds off of your +init time (especially if you have a lot of keybindings). Alternatively, +if you only want to prevent ‘annalist’ from recording certain things or +have it only record certain things, you can configure +‘annalist-record-blacklist’ or ‘annalist-record-whitelist’ respectively. + + +File: annalist.info, Node: Terminology, Next: Settings, Prev: Disabling Annalist, Up: Usage + +1.2 Terminology +=============== + + • item - and individual recorded item; may be displayed as a heading + or as a table column entry (e.g. a key such as ‘C-c’) + • record - a list of related, printable items corresponding to one + piece of information (e.g. a single keybinding: a list of a + keymap, key, and definition) + • metadata - a plist of information about a data list that should not + be printed; appears as the last item in a record + • tome - a collection of records of a specific type + + +File: annalist.info, Node: Settings, Next: Defining New Types, Prev: Terminology, Up: Usage + +1.3 Settings +============ + +Annalist provides ‘annalist-describe-hook’ which is run in annalist +description buffers after they have been populated but before they are +marked read-only: + (add-hook 'annalist-describe-hook + (lambda () (visual-fill-column-mode -1))) + + +File: annalist.info, Node: Defining New Types, Next: Defining Views, Prev: Settings, Up: Usage + +1.4 Defining New Types +====================== + + Three huge tomes bound in worn, cracked dark leather rested on a + large, long stone lectern, as though waiting for three speakers to + step up and read at the same time. + + Annalist provides the function ‘annalist-define-tome’ for defining +new types of tomes: + (annalist-define-tome 'battles + '(:primary-key (year name) + :table-start-index 1 + year + name + casualties + ...)) + + At minimum, a type definition must include ‘:primary-key’, +‘:table-start-index’, and a symbol for each item records should store. +Items should be defined in the order they should appear in org headings +and then in the table. + +* Menu: + +* Type Top-level Settings:: +* Type Item Settings:: +* ‘:record-update’, ‘:preprocess’, and ‘:postprocess’ Settings Argument: record-update preprocess and postprocess Settings Argument. + + +File: annalist.info, Node: Type Top-level Settings, Next: Type Item Settings, Up: Defining New Types + +1.4.1 Type Top-level Settings +----------------------------- + +These settings apply to the entirety of the recorded information. + + • ‘:table-start-index’ - the index of the first item to be printed in + an org table; previous items are printed as headings (default: + none) + • ‘:primary-key’ - the item or list of items that uniquely identifies + the record; used with the ‘:test’ values for those items to check + for an old record that should be replaced/updated (default: none) + • ‘:record-update’ - a function used to update a record before + recording it; this can be used to, for example, set the value of an + item to store the previous value of another item; the function is + called with ‘old-record’ (nil if none), ‘new-record’, and + ‘settings’; see ‘annalist--update-keybindings’ for an example of + how to create such a function (default: none) + • ‘:preprocess’ - a function used to alter a record before doing + anything with it; it is passed ‘record’ and ‘settings’ and should + return the altered record; see the default keybindings type for an + example (default: none) + • ‘:test’ - test function used for comparing the primary key (as a + list of each item in the order it appears in the definition); you + will need to create the test with ‘define-hash-table-test’ if it + does not exist (default: ‘equal’; generally should be unnecessary + to change) + • ‘:defaults’ - a plist of default item settings; see below for valid + item settings (default: none) + + +File: annalist.info, Node: Type Item Settings, Next: record-update preprocess and postprocess Settings Argument, Prev: Type Top-level Settings, Up: Defining New Types + +1.4.2 Type Item Settings +------------------------ + +Item settings only apply to a specific item. Defaults for items that +don't explicitly specify a setting can be set using the top-level +‘:defaults’ keyword. + + • ‘:test’ - test function used for comparing items; only applicable + to heading items; you will need to create the test with + ‘define-hash-table-test’ if it does not exist (default: ‘equal’; + generally should be unnecessary to change) + + +File: annalist.info, Node: record-update preprocess and postprocess Settings Argument, Prev: Type Item Settings, Up: Defining New Types + +1.4.3 ‘:record-update’, ‘:preprocess’, and ‘:postprocess’ Settings Argument +--------------------------------------------------------------------------- + +The settings plist past to the ‘:record-update’ function contains all +information for both the tome type and view. The information is +converted into a valid plist and some extra keywords are added. Here is +an example: + '(:table-start-index 2 + :primary-key (keymap state key) + ;; the following keywords are generated for convenience + :type keybindings + :key-indices (2 1 0) + :final-index 4 + :metadata-index 5 + ;; item settings can be accessed by their symbol or their index + keymap (:name keymap :index 0 :format annalist-code) + 0 (:name keymap :index 0 :format annalist-code) + ...) + + +File: annalist.info, Node: Defining Views, Next: Recording, Prev: Defining New Types, Up: Usage + +1.5 Defining Views +================== + + In those days the company was in service to… + + Views contain settings for formatting and displaying recorded +information. Settings from the type definition cannot be changed later. +On the other hand, views are for all settings that a user may want to +change for a particular ‘annalist-describe’ call. They are defined +using the same format as tome types: + (annalist-define-view 'battles 'default + '(:defaults (:format capitalize) + year + name + (casualties :title "Deaths") + ...)) + + The ‘default’ view is what ‘annalist-describe’ will use if no view +name is explicitly specified. To prevent naming conflicts, external +packages that create views should prefix the views with their symbol +(e.g. ‘general-alternate-view’). + +* Menu: + +* View Top-level Settings:: +* View Item Settings:: + + +File: annalist.info, Node: View Top-level Settings, Next: View Item Settings, Up: Defining Views + +1.5.1 View Top-level Settings +----------------------------- + +These settings apply to the entirety of the recorded information. + + • ‘:predicate’ - a function that is passed the entire record and + returns non-nil if the record should be printed (default: none) + • ‘:sort’ - a function used to sort records in each printed table; + the function is passed two records and and should return non-nil if + the first record should come first (default: none; tables are + printed in recorded order) + • ‘:hooks’ - a function or a list of functions to run in the describe + buffer after printing all headings and tables before making the + buffer readonly; these run before ‘annalist-describe-hook’ + (default: none) + • ‘:postprocess’ - a function used to alter a record just before + printing it; it is passed ‘record’ and ‘settings’ and should return + the altered record; an example use case would be to alter the + record using its metadata (e.g. by replacing a keybinding + definition with a which-key description, if one exists) (default: + none) + • ‘:defaults’ - a plist of default item settings; see below for valid + item settings (default: none) + + There is also a special ‘:inherit’ keyword that can be used to create +a new type of tome that is based on another type: + (annalist-define-view 'keybindings 'alternate + ;; override title for key column + '((key :title "Keybinding") + ...) + :inherit 'keybindings) + + +File: annalist.info, Node: View Item Settings, Prev: View Top-level Settings, Up: Defining Views + +1.5.2 View Item Settings +------------------------ + +Item settings only apply to a specific item. Defaults for items that +don't explicitly specify a setting can be set using the top-level +‘:defaults’ keyword. + (annalist-define-view 'keybindings 'my-view + '(:defaults (:format #'capitalize) + ;; surround key with = instead of capitalizing + (key :format #'annalist-verbatim) + ;; perform no formatting on definition + (definition :format nil))) + + Sorting/filtering (only for items displayed in headings): + • ‘:predicate’ - a function that is passed the item and returns + non-nil if it should be printed; only applicable to heading items + (default: none) + • ‘:prioritize’ - list of items that should be printed before any + others; only applicable to heading items (default: none) + • ‘:sort’ - a function used to sort records; only applicable to + heading items; the function is passed two items and and should + return non-nil if the first item should come first (default: none; + printed in recorded order) + + Formatting: + • ‘:title’ - a description of the item; used as the column title + (default: capitalize the symbol name; local only) + • ‘:format’ - function to run on the item value before it is printed + (e.g. ‘#'capitalize’, ‘#'annalist-code’, ‘#'annalist-verbatim’, + etc.); note that this is run on the item as-is if it has not been + truncated, so the function may need to convert the item to a string + first; has no effect if the item is extracted to a footnote/source + block (default: none) + • ‘:max-width’ - the max character width for an item; note that this + is compared to the item as-is before any formatting (default: 50) + • ‘:extractp’ - function to determine whether to extract longer + entries into footnotes instead of truncating them; (default: + ‘listp’) + • ‘:src-block-p’ function to determine whether to extract to a source + block when the ‘:extractp’ function returns non-nil (default: + ‘listp’) + + +File: annalist.info, Node: Recording, Next: Describing, Prev: Defining Views, Up: Usage + +1.6 Recording +============= + + The Lady said, “I wanted you to see this, Annalist.” […] “What is + about to transpire. So that it is properly recorded in at least + one place.” + + ‘annalist-record’ is used to record information. It requires three +arguments: ‘annalist’ ‘type’ ‘record’. The ‘annalist’ argument will +usually be the same as the package prefix that is recording the data. +‘annalist’ and any other names prefixed by ‘annalist’ are reserved for +this package. ‘type’ is the type of data to record, and ‘record’ is the +actual data. Optionally, the user can also specify metadata that won't +be printed after the final item. Buffer-local records should +additionally specify ‘:local t’. Here is an example: + (annalist-record 'me 'keybindings + (list + ;; keymap state key definition previous-definition + 'global-map nil (kbd "C-+") #'text-scale-increase nil + ;; metadata can be specified after final item + (list :zoom-related-binding t))) + + ;; alternatively, record using plist instead of ordered list + (annalist-record 'me 'keybindings + (list + 'keymap 'global-map + 'state nil + 'key (kbd "C-+") + 'definition #'text-scale-increase + ;; metadata can be specified with `t' key + t (list :zoom-related-binding t)) + :plist t) + + Some items can potentially be recorded as nil. In the previous +example, the evil ‘state’ is recorded as nil (which will always be the +case for non-evil users). When a heading item is nil, the heading at +that level will just be skipped/not printed. + + +File: annalist.info, Node: Describing, Next: Helper Functions, Prev: Recording, Up: Usage + +1.7 Describing +============== + + Once each month, in the evening, the entire Company assembles so + the Annalist can read from his predecessors. + + ‘annalist-describe’ is used to describe information. It takes three +arguments: ‘name’ ‘type view’. ‘view’ is optional (defaults to +‘default’). For example: + (annalist-describe 'me 'keybindings) + + It is possible to have custom filtering/sorting behavior by using a +custom view: + (annalist-define-view 'keybindings 'active-keybindings-only + '((keymap + ;; only show keys bound in active keymaps + :predicate #'annalist--active-keymap + ;; sort keymaps alphabetically + :sort #'annalist--string-<))) + + (annalist-describe 'my 'keybindings 'active-keybindings-only) + + ‘annalist-org-startup-folded’ will determine what +‘org-startup-folded’ setting to use (defaults to nil; all headings will +be unfolded). + + +File: annalist.info, Node: Helper Functions, Next: Builtin Types, Prev: Describing, Up: Usage + +1.8 Helper Functions +==================== + +* Menu: + +* List Helpers:: +* Formatting Helpers:: +* Sorting Helpers:: + + +File: annalist.info, Node: List Helpers, Next: Formatting Helpers, Up: Helper Functions + +1.8.1 List Helpers +------------------ + +‘annalist-plistify-record’ can be used to convert a record that is an +ordered list to a plist. ‘annalist-listify-record’ can be used to do +the opposite. This is what the ‘:plist’ argument for ‘annalist-record’ +uses internally. These functions can be useful, for example, inside a +‘:record-update’ function, so that you can get record items by their +name instead of by their index. However, if there will be a lot of data +recorded for a type during Emacs initialization time, the extra time to +convert between list types can add up, so it's recommended that you +don't use these functions or ‘:plist’ in such cases. + + +File: annalist.info, Node: Formatting Helpers, Next: Sorting Helpers, Prev: List Helpers, Up: Helper Functions + +1.8.2 Formatting Helpers +------------------------ + + 1. ‘:format’ Helpers + + Annalist provides ‘annalist-verbatim’ (e.g. ‘=verbatim text=’), + ‘annalist-code’ (e.g. ‘~my-function~’), and ‘annalist-capitalize’. + There is also an ‘annalist-compose’ helper for combining different + formatting functions. + + 2. Formatting Emacs Lisp Source Blocks + + By default, Emacs Lisp extracted into source blocks will just be + one long line. You can add ‘annalist-multiline-source-blocks’ to a + view's ‘:hooks’ keyword or to ‘annalist-describe-hook’ to + autoformat org source blocks if lispy is installed. By default, it + uses ‘lispy-alt-multiline’. To use ‘lispy-multiline’ instead, + customize ‘annalist-multiline-function’. + + The builtin types have ‘annlist-multiline-source-blocks’ in their + ‘:hooks’ setting by default. + + Here is an example of what this looks like: + +[https://user-images.githubusercontent.com/4250696/62338313-1025e300-b4a6-11e9-845f-179c02abef35] + + +File: annalist.info, Node: Sorting Helpers, Prev: Formatting Helpers, Up: Helper Functions + +1.8.3 Sorting Helpers +--------------------- + +Annalist provides ‘annalist-string-<’ and ‘annalist-key-<’ (e.g. ‘(kbd +"C-c a")’ vs ‘(kbd "C-c b")’). + + +File: annalist.info, Node: Builtin Types, Prev: Helper Functions, Up: Usage + +1.9 Builtin Types +================= + +* Menu: + +* Keybindings Type:: + + +File: annalist.info, Node: Keybindings Type, Up: Builtin Types + +1.9.1 Keybindings Type +---------------------- + +Annalist provides a type for recording keybindings that is used by +‘evil-collection’ and ‘general’. When recording a keybinding, the +keymap must be provided as a symbol. Here is an example: + (annalist-record 'annalist 'keybindings + (list 'org-mode-map nil (kbd "C-c g") #'counsel-org-goto)) + + In addition to the default view, it has a ‘valid’ to only show +keybindings for keymaps/states that exist (since some keybindings may be +in a ‘with-eval-after-load’). It also has an ‘active’ view to only show +keybindings that are currently active. + + +Tag Table: +Node: Top217 +Node: Usage2193 +Node: Disabling Annalist2441 +Node: Terminology3220 +Node: Settings3849 +Node: Defining New Types4233 +Node: Type Top-level Settings5268 +Node: Type Item Settings6983 +Node: record-update preprocess and postprocess Settings Argument7635 +Node: Defining Views8595 +Node: View Top-level Settings9590 +Node: View Item Settings11230 +Node: Recording13451 +Node: Describing15390 +Node: Helper Functions16427 +Node: List Helpers16641 +Node: Formatting Helpers17417 +Node: Sorting Helpers18604 +Node: Builtin Types18866 +Node: Keybindings Type19016 + +End Tag Table + + +Local Variables: +coding: utf-8 +Info-documentlanguage: en +End: diff --git a/straight/build/annalist/annalist.texi b/straight/build/annalist/annalist.texi new file mode 120000 index 0000000..d8eb691 --- /dev/null +++ b/straight/build/annalist/annalist.texi @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/annalist/annalist.texi
\ No newline at end of file diff --git a/straight/build/annalist/dir b/straight/build/annalist/dir new file mode 100644 index 0000000..77a3845 --- /dev/null +++ b/straight/build/annalist/dir @@ -0,0 +1,19 @@ +This is the file .../info/dir, which contains the +topmost node of the Info hierarchy, called (dir)Top. +The first time you invoke Info you start off looking at this node. + +File: dir, Node: Top This is the top of the INFO tree + + This (the Directory node) gives a menu of major topics. + Typing "q" exits, "H" lists all Info commands, "d" returns here, + "h" gives a primer for first-timers, + "mEmacs<Return>" visits the Emacs manual, etc. + + In Emacs, you can click mouse button 2 on a menu item or cross reference + to select it. + +* Menu: + +Emacs +* Annalist: (annalist). Record and display information such as + keybindings. diff --git a/straight/build/bind-key/.github/PULL_REQUEST_TEMPLATE.md b/straight/build/bind-key/.github/PULL_REQUEST_TEMPLATE.md new file mode 120000 index 0000000..7d92aee --- /dev/null +++ b/straight/build/bind-key/.github/PULL_REQUEST_TEMPLATE.md @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/bind-key/.github/PULL_REQUEST_TEMPLATE.md
\ No newline at end of file diff --git a/straight/build/bind-key/bind-key-autoloads.el b/straight/build/bind-key/bind-key-autoloads.el new file mode 100644 index 0000000..3e8194f --- /dev/null +++ b/straight/build/bind-key/bind-key-autoloads.el @@ -0,0 +1,106 @@ +;;; bind-key-autoloads.el --- automatically extracted autoloads (do not edit) -*- lexical-binding: t -*- +;; Generated by the `loaddefs-generate' function. + +;; This file is part of GNU Emacs. + +;;; Code: + + + +;;; Generated autoloads from bind-key.el + +(defvar personal-keybindings nil "\ +List of bindings performed by `bind-key'. + +Elements have the form ((KEY . [MAP]) CMD ORIGINAL-CMD)") +(autoload 'bind-key "bind-key" "\ +Bind KEY-NAME to COMMAND in KEYMAP (`global-map' if not passed). + +KEY-NAME may be a vector, in which case it is passed straight to +`define-key'. Or it may be a string to be interpreted as +spelled-out keystrokes, e.g., \"C-c C-z\". See the documentation +of `edmacro-mode' for details. + +COMMAND must be an interactive function or lambda form. + +KEYMAP, if present, should be a keymap variable or symbol. +For example: + + (bind-key \"M-h\" #\\='some-interactive-function my-mode-map) + + (bind-key \"M-h\" #\\='some-interactive-function \\='my-mode-map) + +If PREDICATE is non-nil, it is a form evaluated to determine when +a key should be bound. It must return non-nil in such cases. +Emacs can evaluate this form at any time that it does redisplay +or operates on menu data structures, so you should write it so it +can safely be called at any time. + +(fn KEY-NAME COMMAND &optional KEYMAP PREDICATE)" nil t) +(autoload 'unbind-key "bind-key" "\ +Unbind the given KEY-NAME, within the KEYMAP (if specified). +See `bind-key' for more details. + +(fn KEY-NAME &optional KEYMAP)" nil t) +(autoload 'bind-key* "bind-key" "\ +Similar to `bind-key', but overrides any mode-specific bindings. + +(fn KEY-NAME COMMAND &optional PREDICATE)" nil t) +(autoload 'bind-keys "bind-key" "\ +Bind multiple keys at once. + +Accepts keyword arguments: +:map MAP - a keymap into which the keybindings should be + added +:prefix KEY - prefix key for these bindings +:prefix-map MAP - name of the prefix map that should be created + for these bindings +:prefix-docstring STR - docstring for the prefix-map variable +:menu-name NAME - optional menu string for prefix map +:repeat-docstring STR - docstring for the repeat-map variable +:repeat-map MAP - name of the repeat map that should be created + for these bindings. If specified, the + `repeat-map' property of each command bound + (within the scope of the `:repeat-map' keyword) + is set to this map. +:exit BINDINGS - Within the scope of `:repeat-map' will bind the + key in the repeat map, but will not set the + `repeat-map' property of the bound command. +:continue BINDINGS - Within the scope of `:repeat-map' forces the + same behavior as if no special keyword had + been used (that is, the command is bound, and + it's `repeat-map' property set) +:continue-only BINDINGS - Within the scope of `:repeat-map', will make + the command continue but not enter the repeat + map, via the `repeat-continue' property +:filter FORM - optional form to determine when bindings apply + +The rest of the arguments are conses of keybinding string and a +function symbol (unquoted). + +(fn &rest ARGS)" nil t) +(autoload 'bind-keys* "bind-key" "\ +Bind multiple keys at once, in `override-global-map'. +Accepts the same keyword arguments as `bind-keys' (which see). + +This binds keys in such a way that bindings are not overridden by +other modes. See `override-global-mode'. + +(fn &rest ARGS)" nil t) +(autoload 'describe-personal-keybindings "bind-key" "\ +Display all the personal keybindings defined by `bind-key'." t) +(register-definition-prefixes "bind-key" '("bind-key" "override-global-m")) + +;;; End of scraped data + +(provide 'bind-key-autoloads) + +;; Local Variables: +;; version-control: never +;; no-byte-compile: t +;; no-update-autoloads: t +;; no-native-compile: t +;; coding: utf-8-emacs-unix +;; End: + +;;; bind-key-autoloads.el ends here diff --git a/straight/build/bind-key/bind-key-pkg.el b/straight/build/bind-key/bind-key-pkg.el new file mode 120000 index 0000000..089df98 --- /dev/null +++ b/straight/build/bind-key/bind-key-pkg.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/bind-key/bind-key-pkg.el
\ No newline at end of file diff --git a/straight/build/bind-key/bind-key.el b/straight/build/bind-key/bind-key.el new file mode 120000 index 0000000..3a98282 --- /dev/null +++ b/straight/build/bind-key/bind-key.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/bind-key/bind-key.el
\ No newline at end of file diff --git a/straight/build/bind-key/bind-key.elc b/straight/build/bind-key/bind-key.elc Binary files differnew file mode 100644 index 0000000..3618811 --- /dev/null +++ b/straight/build/bind-key/bind-key.elc diff --git a/straight/build/diminish/.github/PULL_REQUEST_TEMPLATE.md b/straight/build/diminish/.github/PULL_REQUEST_TEMPLATE.md new file mode 120000 index 0000000..e98de24 --- /dev/null +++ b/straight/build/diminish/.github/PULL_REQUEST_TEMPLATE.md @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/diminish/.github/PULL_REQUEST_TEMPLATE.md
\ No newline at end of file diff --git a/straight/build/diminish/README.md b/straight/build/diminish/README.md new file mode 120000 index 0000000..b766b70 --- /dev/null +++ b/straight/build/diminish/README.md @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/diminish/README.md
\ No newline at end of file diff --git a/straight/build/diminish/diminish-autoloads.el b/straight/build/diminish/diminish-autoloads.el new file mode 100644 index 0000000..1006a3f --- /dev/null +++ b/straight/build/diminish/diminish-autoloads.el @@ -0,0 +1,61 @@ +;;; diminish-autoloads.el --- automatically extracted autoloads (do not edit) -*- lexical-binding: t -*- +;; Generated by the `loaddefs-generate' function. + +;; This file is part of GNU Emacs. + +;;; Code: + + + +;;; Generated autoloads from diminish.el + +(autoload 'diminish "diminish" "\ +Diminish mode-line display of minor mode MODE to TO-WHAT (default \"\"). + +Interactively, enter (with completion) the name of any minor mode, followed +on the next line by what you want it diminished to (default empty string). +The response to neither prompt should be quoted. However, in Lisp code, +both args must be quoted, the first as a symbol, the second as a string, +as in (diminish \\='jiggle-mode \" Jgl\"). + +The mode-line displays of minor modes usually begin with a space, so +the modes' names appear as separate words on the mode line. However, if +you're having problems with a cramped mode line, you may choose to use single +letters for some modes, without leading spaces. Capitalizing them works +best; if you then diminish some mode to \"X\" but have `abbrev-mode' enabled as +well, you'll get a display like \"AbbrevX\". This function prepends a space +to TO-WHAT if it's > 1 char long & doesn't already begin with a space. + +(fn MODE &optional TO-WHAT)" t) +(autoload 'diminish-undo "diminish" "\ +Restore mode-line display of diminished mode MODE to its minor-mode value. +Do nothing if the arg is a minor mode that hasn't been diminished. + +Interactively, enter (with completion) the name of any diminished mode (a +mode that was formerly a minor mode on which you invoked \\[diminish]). +To restore all diminished modes to minor status, answer `diminished-modes'. +The response to the prompt shouldn't be quoted. However, in Lisp code, +the arg must be quoted as a symbol, as in (diminish-undo \\='diminished-modes). + +(fn MODE)" t) +(autoload 'diminished-modes "diminish" "\ +Echo all active diminished or minor modes as if they were minor. +The display goes in the echo area; if it's too long even for that, +you can see the whole thing in the *Messages* buffer. +This doesn't change the status of any modes; it just lets you see +what diminished modes would be on the mode-line if they were still minor." t) +(register-definition-prefixes "diminish" '("diminish")) + +;;; End of scraped data + +(provide 'diminish-autoloads) + +;; Local Variables: +;; version-control: never +;; no-byte-compile: t +;; no-update-autoloads: t +;; no-native-compile: t +;; coding: utf-8-emacs-unix +;; End: + +;;; diminish-autoloads.el ends here diff --git a/straight/build/diminish/diminish-pkg.el b/straight/build/diminish/diminish-pkg.el new file mode 120000 index 0000000..c486735 --- /dev/null +++ b/straight/build/diminish/diminish-pkg.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/diminish/diminish-pkg.el
\ No newline at end of file diff --git a/straight/build/diminish/diminish.el b/straight/build/diminish/diminish.el new file mode 120000 index 0000000..2ff9eae --- /dev/null +++ b/straight/build/diminish/diminish.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/diminish/diminish.el
\ No newline at end of file diff --git a/straight/build/diminish/diminish.elc b/straight/build/diminish/diminish.elc Binary files differnew file mode 100644 index 0000000..22545ba --- /dev/null +++ b/straight/build/diminish/diminish.elc diff --git a/straight/build/evil-collection/evil-collection-autoloads.el b/straight/build/evil-collection/evil-collection-autoloads.el new file mode 100644 index 0000000..d0693e0 --- /dev/null +++ b/straight/build/evil-collection/evil-collection-autoloads.el @@ -0,0 +1,108 @@ +;;; evil-collection-autoloads.el --- automatically extracted autoloads (do not edit) -*- lexical-binding: t -*- +;; Generated by the `loaddefs-generate' function. + +;; This file is part of GNU Emacs. + +;;; Code: + + + +;;; Generated autoloads from evil-collection.el + +(autoload 'evil-collection-translate-minor-mode-key "evil-collection" "\ +Translate keys in the keymap(s) corresponding to STATES and MODES. + +Similar to `evil-collection-translate-key' but for minor modes. +STATES should be the name of an evil state, a list of states, or nil. MODES +should be a symbol corresponding to minor-mode to make the translations in or a +list of minor-mode symbols. TRANSLATIONS corresponds to a list of +key replacement pairs. For example, specifying \"a\" \"b\" will bind \"a\" to +\"b\"'s definition in the keymap. Specifying nil as a replacement will unbind a +key. If DESTRUCTIVE is nil, a backup of the keymap will be stored on the initial +invocation, and future invocations will always look up keys in the backup +keymap. When no TRANSLATIONS are given, this function will only create the +backup keymap without making any translations. On the other hand, if DESTRUCTIVE +is non-nil, the keymap will be destructively altered without creating a backup. +For example, calling this function multiple times with \"a\" \"b\" \"b\" \"a\" +would continue to swap and unswap the definitions of these keys. This means that +when DESTRUCTIVE is non-nil, all related swaps/cycles should be done in the same +invocation. + +(fn STATES MODES &rest TRANSLATIONS &key DESTRUCTIVE &allow-other-keys)") +(function-put 'evil-collection-translate-minor-mode-key 'lisp-indent-function 'defun) +(autoload 'evil-collection-translate-key "evil-collection" "\ +Translate keys in the keymap(s) corresponding to STATES and KEYMAPS. +STATES should be the name of an evil state, a list of states, or nil. KEYMAPS +should be a symbol corresponding to the keymap to make the translations in or a +list of keymap symbols. Like `evil-define-key', when a keymap does not exist, +the keybindings will be deferred until the keymap is defined, so +`with-eval-after-load' is not necessary. TRANSLATIONS corresponds to a list of +key replacement pairs. For example, specifying \"a\" \"b\" will bind \"a\" to +\"b\"'s definition in the keymap. Specifying nil as a replacement will unbind a +key. If DESTRUCTIVE is nil, a backup of the keymap will be stored on the initial +invocation, and future invocations will always look up keys in the backup +keymap. When no TRANSLATIONS are given, this function will only create the +backup keymap without making any translations. On the other hand, if DESTRUCTIVE +is non-nil, the keymap will be destructively altered without creating a backup. +For example, calling this function multiple times with \"a\" \"b\" \"b\" \"a\" +would continue to swap and unswap the definitions of these keys. This means that +when DESTRUCTIVE is non-nil, all related swaps/cycles should be done in the same +invocation. + +(fn STATES KEYMAPS &rest TRANSLATIONS &key DESTRUCTIVE &allow-other-keys)") +(function-put 'evil-collection-translate-key 'lisp-indent-function 'defun) +(autoload 'evil-collection-swap-key "evil-collection" "\ +Wrapper around `evil-collection-translate-key' for swapping keys. +STATES, KEYMAPS, and ARGS are passed to `evil-collection-translate-key'. ARGS +should consist of key swaps (e.g. \"a\" \"b\" is equivalent to \"a\" \"b\" \"b\" +\"a\" with `evil-collection-translate-key') and optionally keyword arguments for +`evil-collection-translate-key'. + +(fn STATES KEYMAPS &rest ARGS)" nil t) +(function-put 'evil-collection-swap-key 'lisp-indent-function 'defun) +(autoload 'evil-collection-swap-minor-mode-key "evil-collection" "\ +Wrapper around `evil-collection-translate-minor-mode-key' for swapping keys. +STATES, MODES, and ARGS are passed to +`evil-collection-translate-minor-mode-key'. ARGS should consist of key swaps +(e.g. \"a\" \"b\" is equivalent to \"a\" \"b\" \"b\" \"a\" +with `evil-collection-translate-minor-mode-key') and optionally keyword +arguments for `evil-collection-translate-minor-mode-key'. + +(fn STATES MODES &rest ARGS)" nil t) +(function-put 'evil-collection-swap-minor-mode-key 'lisp-indent-function 'defun) +(autoload 'evil-collection-require "evil-collection" "\ +Require the evil-collection-MODE file, but do not activate it. + +MODE should be a symbol. This requires the evil-collection-MODE +feature without needing to manipulate `load-path'. NOERROR is +forwarded to `require'. + +(fn MODE &optional NOERROR)") +(autoload 'evil-collection-init "evil-collection" "\ +Register the Evil bindings for all modes in `evil-collection-mode-list'. + +Alternatively, you may register select bindings manually, for +instance: + + (with-eval-after-load ='calendar + (evil-collection-calendar-setup)) + +If MODES is specified (as either one mode or a list of modes), use those modes +instead of the modes in `evil-collection-mode-list'. + +(fn &optional MODES)" t) +(register-definition-prefixes "evil-collection" '("evil-collection-")) + +;;; End of scraped data + +(provide 'evil-collection-autoloads) + +;; Local Variables: +;; version-control: never +;; no-byte-compile: t +;; no-update-autoloads: t +;; no-native-compile: t +;; coding: utf-8-emacs-unix +;; End: + +;;; evil-collection-autoloads.el ends here diff --git a/straight/build/evil-collection/evil-collection.el b/straight/build/evil-collection/evil-collection.el new file mode 120000 index 0000000..f352d08 --- /dev/null +++ b/straight/build/evil-collection/evil-collection.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/evil-collection/evil-collection.el
\ No newline at end of file diff --git a/straight/build/evil-collection/evil-collection.elc b/straight/build/evil-collection/evil-collection.elc Binary files differnew file mode 100644 index 0000000..e54de24 --- /dev/null +++ b/straight/build/evil-collection/evil-collection.elc diff --git a/straight/build/evil/evil-autoloads.el b/straight/build/evil/evil-autoloads.el new file mode 100644 index 0000000..085b7f4 --- /dev/null +++ b/straight/build/evil/evil-autoloads.el @@ -0,0 +1,114 @@ +;;; evil-autoloads.el --- automatically extracted autoloads (do not edit) -*- lexical-binding: t -*- +;; Generated by the `loaddefs-generate' function. + +;; This file is part of GNU Emacs. + +;;; Code: + + + +;;; Generated autoloads from evil-command-window.el + +(register-definition-prefixes "evil-command-window" '("evil-")) + + +;;; Generated autoloads from evil-commands.el + +(register-definition-prefixes "evil-commands" '("evil-")) + + +;;; Generated autoloads from evil-common.el + +(register-definition-prefixes "evil-common" '("bounds-of-evil-" "evil-" "forward-evil-")) + + +;;; Generated autoloads from evil-core.el + + (autoload 'evil-mode "evil" nil t) +(register-definition-prefixes "evil-core" '("evil-" "turn-o")) + + +;;; Generated autoloads from evil-digraphs.el + +(autoload 'evil-digraph "evil-digraphs" "\ +Convert DIGRAPH to character or list representation. +If DIGRAPH is a list (CHAR1 CHAR2), return the corresponding character; +if DIGRAPH is a character, return the corresponding list. +Searches in `evil-digraphs-table-user' and `evil-digraphs-table'. + +(fn DIGRAPH)") +(register-definition-prefixes "evil-digraphs" '("evil-digraphs-table")) + + +;;; Generated autoloads from evil-ex.el + +(register-definition-prefixes "evil-ex" '("evil-")) + + +;;; Generated autoloads from evil-integration.el + +(register-definition-prefixes "evil-integration" '("evil-")) + + +;;; Generated autoloads from evil-jumps.el + +(register-definition-prefixes "evil-jumps" '("evil-")) + + +;;; Generated autoloads from evil-keybindings.el + +(register-definition-prefixes "evil-keybindings" '("evil--set-motion-state")) + + +;;; Generated autoloads from evil-macros.el + +(register-definition-prefixes "evil-macros" '("evil-")) + + +;;; Generated autoloads from evil-maps.el + +(register-definition-prefixes "evil-maps" '("evil-")) + + +;;; Generated autoloads from evil-repeat.el + +(register-definition-prefixes "evil-repeat" '("evil-")) + + +;;; Generated autoloads from evil-search.el + +(register-definition-prefixes "evil-search" '("evil-")) + + +;;; Generated autoloads from evil-states.el + +(register-definition-prefixes "evil-states" '("evil-")) + + +;;; Generated autoloads from evil-test-helpers.el + +(register-definition-prefixes "evil-test-helpers" '("evil-")) + + +;;; Generated autoloads from evil-types.el + +(register-definition-prefixes "evil-types" '("evil-ex-get-optional-register-and-count")) + + +;;; Generated autoloads from evil-vars.el + +(register-definition-prefixes "evil-vars" '("evil-")) + +;;; End of scraped data + +(provide 'evil-autoloads) + +;; Local Variables: +;; version-control: never +;; no-byte-compile: t +;; no-update-autoloads: t +;; no-native-compile: t +;; coding: utf-8-emacs-unix +;; End: + +;;; evil-autoloads.el ends here diff --git a/straight/build/evil/evil-command-window.el b/straight/build/evil/evil-command-window.el new file mode 120000 index 0000000..61402d1 --- /dev/null +++ b/straight/build/evil/evil-command-window.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/evil/evil-command-window.el
\ No newline at end of file diff --git a/straight/build/evil/evil-command-window.elc b/straight/build/evil/evil-command-window.elc Binary files differnew file mode 100644 index 0000000..98fc1da --- /dev/null +++ b/straight/build/evil/evil-command-window.elc diff --git a/straight/build/evil/evil-commands.el b/straight/build/evil/evil-commands.el new file mode 120000 index 0000000..152d552 --- /dev/null +++ b/straight/build/evil/evil-commands.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/evil/evil-commands.el
\ No newline at end of file diff --git a/straight/build/evil/evil-commands.elc b/straight/build/evil/evil-commands.elc Binary files differnew file mode 100644 index 0000000..3fd5e60 --- /dev/null +++ b/straight/build/evil/evil-commands.elc diff --git a/straight/build/evil/evil-common.el b/straight/build/evil/evil-common.el new file mode 120000 index 0000000..2ab2d78 --- /dev/null +++ b/straight/build/evil/evil-common.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/evil/evil-common.el
\ No newline at end of file diff --git a/straight/build/evil/evil-common.elc b/straight/build/evil/evil-common.elc Binary files differnew file mode 100644 index 0000000..0dba496 --- /dev/null +++ b/straight/build/evil/evil-common.elc diff --git a/straight/build/evil/evil-core.el b/straight/build/evil/evil-core.el new file mode 120000 index 0000000..250a442 --- /dev/null +++ b/straight/build/evil/evil-core.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/evil/evil-core.el
\ No newline at end of file diff --git a/straight/build/evil/evil-core.elc b/straight/build/evil/evil-core.elc Binary files differnew file mode 100644 index 0000000..97015ab --- /dev/null +++ b/straight/build/evil/evil-core.elc diff --git a/straight/build/evil/evil-development.el b/straight/build/evil/evil-development.el new file mode 120000 index 0000000..419c5d8 --- /dev/null +++ b/straight/build/evil/evil-development.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/evil/evil-development.el
\ No newline at end of file diff --git a/straight/build/evil/evil-development.elc b/straight/build/evil/evil-development.elc Binary files differnew file mode 100644 index 0000000..8f17125 --- /dev/null +++ b/straight/build/evil/evil-development.elc diff --git a/straight/build/evil/evil-digraphs.el b/straight/build/evil/evil-digraphs.el new file mode 120000 index 0000000..9434165 --- /dev/null +++ b/straight/build/evil/evil-digraphs.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/evil/evil-digraphs.el
\ No newline at end of file diff --git a/straight/build/evil/evil-digraphs.elc b/straight/build/evil/evil-digraphs.elc Binary files differnew file mode 100644 index 0000000..616d5ac --- /dev/null +++ b/straight/build/evil/evil-digraphs.elc diff --git a/straight/build/evil/evil-ex.el b/straight/build/evil/evil-ex.el new file mode 120000 index 0000000..329f9bd --- /dev/null +++ b/straight/build/evil/evil-ex.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/evil/evil-ex.el
\ No newline at end of file diff --git a/straight/build/evil/evil-ex.elc b/straight/build/evil/evil-ex.elc Binary files differnew file mode 100644 index 0000000..4c3616d --- /dev/null +++ b/straight/build/evil/evil-ex.elc diff --git a/straight/build/evil/evil-integration.el b/straight/build/evil/evil-integration.el new file mode 120000 index 0000000..fbc2e63 --- /dev/null +++ b/straight/build/evil/evil-integration.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/evil/evil-integration.el
\ No newline at end of file diff --git a/straight/build/evil/evil-integration.elc b/straight/build/evil/evil-integration.elc Binary files differnew file mode 100644 index 0000000..d9e712d --- /dev/null +++ b/straight/build/evil/evil-integration.elc diff --git a/straight/build/evil/evil-jumps.el b/straight/build/evil/evil-jumps.el new file mode 120000 index 0000000..938db80 --- /dev/null +++ b/straight/build/evil/evil-jumps.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/evil/evil-jumps.el
\ No newline at end of file diff --git a/straight/build/evil/evil-jumps.elc b/straight/build/evil/evil-jumps.elc Binary files differnew file mode 100644 index 0000000..1088928 --- /dev/null +++ b/straight/build/evil/evil-jumps.elc diff --git a/straight/build/evil/evil-keybindings.el b/straight/build/evil/evil-keybindings.el new file mode 120000 index 0000000..19c5d82 --- /dev/null +++ b/straight/build/evil/evil-keybindings.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/evil/evil-keybindings.el
\ No newline at end of file diff --git a/straight/build/evil/evil-keybindings.elc b/straight/build/evil/evil-keybindings.elc Binary files differnew file mode 100644 index 0000000..249f8cd --- /dev/null +++ b/straight/build/evil/evil-keybindings.elc diff --git a/straight/build/evil/evil-macros.el b/straight/build/evil/evil-macros.el new file mode 120000 index 0000000..64a8cb3 --- /dev/null +++ b/straight/build/evil/evil-macros.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/evil/evil-macros.el
\ No newline at end of file diff --git a/straight/build/evil/evil-macros.elc b/straight/build/evil/evil-macros.elc Binary files differnew file mode 100644 index 0000000..bb5acf9 --- /dev/null +++ b/straight/build/evil/evil-macros.elc diff --git a/straight/build/evil/evil-maps.el b/straight/build/evil/evil-maps.el new file mode 120000 index 0000000..d0e915a --- /dev/null +++ b/straight/build/evil/evil-maps.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/evil/evil-maps.el
\ No newline at end of file diff --git a/straight/build/evil/evil-maps.elc b/straight/build/evil/evil-maps.elc Binary files differnew file mode 100644 index 0000000..da24209 --- /dev/null +++ b/straight/build/evil/evil-maps.elc diff --git a/straight/build/evil/evil-repeat.el b/straight/build/evil/evil-repeat.el new file mode 120000 index 0000000..ee70cf1 --- /dev/null +++ b/straight/build/evil/evil-repeat.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/evil/evil-repeat.el
\ No newline at end of file diff --git a/straight/build/evil/evil-repeat.elc b/straight/build/evil/evil-repeat.elc Binary files differnew file mode 100644 index 0000000..b7fa1ee --- /dev/null +++ b/straight/build/evil/evil-repeat.elc diff --git a/straight/build/evil/evil-search.el b/straight/build/evil/evil-search.el new file mode 120000 index 0000000..fc1fdd2 --- /dev/null +++ b/straight/build/evil/evil-search.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/evil/evil-search.el
\ No newline at end of file diff --git a/straight/build/evil/evil-search.elc b/straight/build/evil/evil-search.elc Binary files differnew file mode 100644 index 0000000..c742ddb --- /dev/null +++ b/straight/build/evil/evil-search.elc diff --git a/straight/build/evil/evil-states.el b/straight/build/evil/evil-states.el new file mode 120000 index 0000000..7c37c3c --- /dev/null +++ b/straight/build/evil/evil-states.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/evil/evil-states.el
\ No newline at end of file diff --git a/straight/build/evil/evil-states.elc b/straight/build/evil/evil-states.elc Binary files differnew file mode 100644 index 0000000..9a21d43 --- /dev/null +++ b/straight/build/evil/evil-states.elc diff --git a/straight/build/evil/evil-test-helpers.el b/straight/build/evil/evil-test-helpers.el new file mode 120000 index 0000000..6e6a843 --- /dev/null +++ b/straight/build/evil/evil-test-helpers.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/evil/evil-test-helpers.el
\ No newline at end of file diff --git a/straight/build/evil/evil-test-helpers.elc b/straight/build/evil/evil-test-helpers.elc Binary files differnew file mode 100644 index 0000000..ba5ffd4 --- /dev/null +++ b/straight/build/evil/evil-test-helpers.elc diff --git a/straight/build/evil/evil-types.el b/straight/build/evil/evil-types.el new file mode 120000 index 0000000..c897b49 --- /dev/null +++ b/straight/build/evil/evil-types.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/evil/evil-types.el
\ No newline at end of file diff --git a/straight/build/evil/evil-types.elc b/straight/build/evil/evil-types.elc Binary files differnew file mode 100644 index 0000000..60bb724 --- /dev/null +++ b/straight/build/evil/evil-types.elc diff --git a/straight/build/evil/evil-vars.el b/straight/build/evil/evil-vars.el new file mode 120000 index 0000000..e7722a6 --- /dev/null +++ b/straight/build/evil/evil-vars.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/evil/evil-vars.el
\ No newline at end of file diff --git a/straight/build/evil/evil-vars.elc b/straight/build/evil/evil-vars.elc Binary files differnew file mode 100644 index 0000000..3aa6d3e --- /dev/null +++ b/straight/build/evil/evil-vars.elc diff --git a/straight/build/evil/evil.el b/straight/build/evil/evil.el new file mode 120000 index 0000000..cab12a7 --- /dev/null +++ b/straight/build/evil/evil.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/evil/evil.el
\ No newline at end of file diff --git a/straight/build/evil/evil.elc b/straight/build/evil/evil.elc Binary files differnew file mode 100644 index 0000000..87421a3 --- /dev/null +++ b/straight/build/evil/evil.elc diff --git a/straight/build/goto-chg/goto-chg-autoloads.el b/straight/build/goto-chg/goto-chg-autoloads.el new file mode 100644 index 0000000..13f475b --- /dev/null +++ b/straight/build/goto-chg/goto-chg-autoloads.el @@ -0,0 +1,57 @@ +;;; goto-chg-autoloads.el --- automatically extracted autoloads (do not edit) -*- lexical-binding: t -*- +;; Generated by the `loaddefs-generate' function. + +;; This file is part of GNU Emacs. + +;;; Code: + + + +;;; Generated autoloads from goto-chg.el + +(autoload 'goto-last-change "goto-chg" "\ +Go to the point where the last edit was made in the current buffer. +Repeat the command to go to the second last edit, etc. + +To go back to more recent edit, the reverse of this command, use \\[goto-last-change-reverse] +or precede this command with \\[universal-argument] - (minus). + +It does not go to the same point twice even if there has been many edits +there. I call the minimal distance between distinguishable edits \"span\". +Set variable `glc-default-span' to control how close is \"the same point\". +Default span is 8. +The span can be changed temporarily with \\[universal-argument] right before \\[goto-last-change]: +\\[universal-argument] <NUMBER> set current span to that number, +\\[universal-argument] (no number) multiplies span by 4, starting with default. +The so set span remains until it is changed again with \\[universal-argument], or the consecutive +repetition of this command is ended by any other command. + +When span is zero (i.e. \\[universal-argument] 0) subsequent \\[goto-last-change] visits each and +every point of edit and a message shows what change was made there. +In this case it may go to the same point twice. + +This command uses undo information. If undo is disabled, so is this command. +At times, when undo information becomes too large, the oldest information is +discarded. See variable `undo-limit'. + +(fn ARG)" t) +(autoload 'goto-last-change-reverse "goto-chg" "\ +Go back to more recent changes after \\[goto-last-change] have been used. +See `goto-last-change' for use of prefix argument. + +(fn ARG)" t) +(register-definition-prefixes "goto-chg" '("glc-")) + +;;; End of scraped data + +(provide 'goto-chg-autoloads) + +;; Local Variables: +;; version-control: never +;; no-byte-compile: t +;; no-update-autoloads: t +;; no-native-compile: t +;; coding: utf-8-emacs-unix +;; End: + +;;; goto-chg-autoloads.el ends here diff --git a/straight/build/goto-chg/goto-chg.el b/straight/build/goto-chg/goto-chg.el new file mode 120000 index 0000000..bf00a2c --- /dev/null +++ b/straight/build/goto-chg/goto-chg.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/goto-chg/goto-chg.el
\ No newline at end of file diff --git a/straight/build/goto-chg/goto-chg.elc b/straight/build/goto-chg/goto-chg.elc Binary files differnew file mode 100644 index 0000000..6945d58 --- /dev/null +++ b/straight/build/goto-chg/goto-chg.elc diff --git a/straight/build/straight/straight-autoloads.el b/straight/build/straight/straight-autoloads.el new file mode 100644 index 0000000..dd6c181 --- /dev/null +++ b/straight/build/straight/straight-autoloads.el @@ -0,0 +1,456 @@ +;;; straight-autoloads.el --- automatically extracted autoloads (do not edit) -*- lexical-binding: t -*- +;; Generated by the `loaddefs-generate' function. + +;; This file is part of GNU Emacs. + +;;; Code: + + + +;;; Generated autoloads from straight.el + +(autoload 'straight-remove-unused-repos "straight" "\ +Remove unused repositories from the repos and build directories. +A repo is considered \"unused\" if it was not explicitly requested via +`straight-use-package' during the current Emacs session. +If FORCE is non-nil do not prompt before deleting repos. + +(fn &optional FORCE)" t) +(autoload 'straight-get-recipe "straight" "\ +Interactively select a recipe from one of the recipe repositories. +All recipe repositories in `straight-recipe-repositories' will +first be cloned. After the recipe is selected, it will be copied +to the kill ring. With a prefix argument, first prompt for a +recipe repository to search. Only that repository will be +cloned. + +From Lisp code, SOURCES should be a subset of the symbols in +`straight-recipe-repositories'. Only those recipe repositories +are cloned and searched. If it is nil or omitted, then the value +of `straight-recipe-repositories' is used. If SOURCES is the +symbol `interactive', then the user is prompted to select a +recipe repository, and a list containing that recipe repository +is used for the value of SOURCES. ACTION may be `copy' (copy +recipe to the kill ring), `insert' (insert at point), or nil (no +action, just return it). + +Optional arg FILTER must be a unary function. +It takes a package name as its sole argument. +If it returns nil the candidate is excluded. + +USE-CACHE non-nil means respect the existing straight.el recipe cache, +i.e. display also packages that have been registered in the current +Emacs session even if not found in any recipe repository, and if such a +package is selected, return just the package name as a symbol, instead +of a recipe. (It is not possible to return an actual recipe, as the API +for `straight-get-recipe' returns MELPA-style recipes, while cached +recipes have already been converted into the internal format.) + +Within `straight-get-recipe', the symbol `cache' is treated as if it is +also a member of `straight-recipe-repositories', and refers to the set +of packages that have already been registered in the current Emacs +session. + +(fn &optional SOURCES ACTION FILTER USE-CACHE)" t) +(autoload 'straight-visit-package-website "straight" "\ +Visit the package RECIPE's website. + +(fn RECIPE)" t) +(autoload 'straight-visit-package "straight" "\ +Open PACKAGE's local repository directory. +When BUILD is non-nil visit PACKAGE's build directory. + +(fn PACKAGE &optional BUILD)" t) +(autoload 'straight-use-package "straight" "\ +Register, clone, build, and activate a package and its dependencies. +This is the main entry point to the functionality of straight.el. + +MELPA-STYLE-RECIPE is either a symbol naming a package, or a list +whose car is a symbol naming a package and whose cdr is a +property list containing e.g. `:type', `:local-repo', `:files', +and VC backend specific keywords. + +First, the package recipe is registered with straight.el. If +NO-CLONE is a function, then it is called with two arguments: the +package name as a string, and a boolean value indicating whether +the local repository for the package is available. In that case, +the return value of the function is used as the value of NO-CLONE +instead. In any case, if NO-CLONE is non-nil, then processing +stops here. + +Otherwise, the repository is cloned, if it is missing. If +NO-BUILD is a function, then it is called with one argument: the +package name as a string. In that case, the return value of the +function is used as the value of NO-BUILD instead. In any case, +if NO-BUILD is non-nil, then processing halts here. Otherwise, +the package is built and activated. Note that if the package +recipe has a nil `:build' entry, then NO-BUILD is ignored +and processing always stops before building and activation +occurs. + +CAUSE is a string explaining the reason why +`straight-use-package' has been called. It is for internal use +only, and is used to construct progress messages. INTERACTIVE is +non-nil if the function has been called interactively. It is for +internal use only, and is used to determine whether to show a +hint about how to install the package permanently. + +Return non-nil when package is initially installed, nil otherwise. + +Interactively, prompt with a list of available packages in currently +registered recipe repositories. With prefix arg, prompt first for which +recipe repository to list from. If a package has already been registered +in the current Emacs session, the existing recipe is re-used rather than +being looked up anew. With prefix arg, \"cache\" is displayed as one of +the recipe repositories, and allows filtering to only already-registered +packages. + +(fn MELPA-STYLE-RECIPE &optional NO-CLONE NO-BUILD CAUSE INTERACTIVE)" t) +(autoload 'straight-register-package "straight" "\ +Register a package without cloning, building, or activating it. +This function is equivalent to calling `straight-use-package' +with a non-nil argument for NO-CLONE. It is provided for +convenience. MELPA-STYLE-RECIPE is as for +`straight-use-package'. + +(fn MELPA-STYLE-RECIPE)") +(autoload 'straight-use-package-no-build "straight" "\ +Register and clone a package without building it. +This function is equivalent to calling `straight-use-package' +with nil for NO-CLONE but a non-nil argument for NO-BUILD. It is +provided for convenience. MELPA-STYLE-RECIPE is as for +`straight-use-package'. + +(fn MELPA-STYLE-RECIPE)") +(autoload 'straight-use-package-lazy "straight" "\ +Register, build, and activate a package if it is already cloned. +This function is equivalent to calling `straight-use-package' +with symbol `lazy' for NO-CLONE. It is provided for convenience. +MELPA-STYLE-RECIPE is as for `straight-use-package'. + +Argument CAUSE is for internal use only. + +(fn MELPA-STYLE-RECIPE &optional CAUSE)") +(autoload 'straight-use-recipes "straight" "\ +Register a recipe repository using MELPA-STYLE-RECIPE. +This registers the recipe and builds it if it is already cloned. +Note that you probably want the recipe for a recipe repository to +include a nil `:build' property, to unconditionally +inhibit the build phase. + +This function also adds the recipe repository to +`straight-recipe-repositories', at the end of the list. + +Existing recipe repositories are not searched for a recipe for the +recipe repository you are trying to register, because that is strange +and confusing. If you explicitly want this behavior, you can use the +`straight-use-package' API directly. + +Argument CAUSE is for internal use only. + +(fn MELPA-STYLE-RECIPE &optional CAUSE)") +(autoload 'straight-override-recipe "straight" "\ +Register MELPA-STYLE-RECIPE as a recipe override. +This puts it in `straight-recipe-overrides', depending on the +value of `straight-current-profile'. + +(fn MELPA-STYLE-RECIPE)") +(autoload 'straight-check-package "straight" "\ +Rebuild a PACKAGE if it has been modified. +PACKAGE is a string naming a package. Interactively, select +PACKAGE from the known packages in the current Emacs session +using `completing-read'. See also `straight-rebuild-package' and +`straight-check-all'. + +(fn PACKAGE)" t) +(autoload 'straight-check-all "straight" "\ +Rebuild any packages that have been modified. +See also `straight-rebuild-all' and `straight-check-package'. +This function should not be called during init." t) +(autoload 'straight-rebuild-package "straight" "\ +Rebuild a PACKAGE. +PACKAGE is a string naming a package. Interactively, select +PACKAGE from the known packages in the current Emacs session +using `completing-read'. With prefix argument RECURSIVE, rebuild +all dependencies as well. See also `straight-check-package' and +`straight-rebuild-all'. + +(fn PACKAGE &optional RECURSIVE)" t) +(autoload 'straight-rebuild-all "straight" "\ +Rebuild all packages. +See also `straight-check-all' and `straight-rebuild-package'." t) +(autoload 'straight-prune-build-cache "straight" "\ +Prune the build cache. +This means that only packages that were built in the last init +run and subsequent interactive session will remain; other +packages will have their build mtime information and any cached +autoloads discarded.") +(autoload 'straight-prune-build-directory "straight" "\ +Prune the build directory. +This means that only packages that were built in the last init +run and subsequent interactive session will remain; other +packages will have their build directories deleted.") +(autoload 'straight-prune-build "straight" "\ +Prune the build cache and build directory. +This means that only packages that were built in the last init +run and subsequent interactive session will remain; other +packages will have their build mtime information discarded and +their build directories deleted." t) +(autoload 'straight-normalize-package "straight" "\ +Normalize a PACKAGE's local repository to its recipe's configuration. +PACKAGE is a string naming a package. Interactively, select +PACKAGE from the known packages in the current Emacs session +using `completing-read'. + +CONVERT-SNAPSHOTS non-nil (interactively, prefix arg) means if the +repository is a snapshot, convert it to a full repository first. + +(fn PACKAGE &key CONVERT-SNAPSHOTS)" t) +(autoload 'straight-normalize-all "straight" "\ +Normalize all packages. See `straight-normalize-package'. +Return a list of recipes for packages that were not successfully +normalized. If multiple packages come from the same local +repository, only one is normalized. + +PREDICATE, if provided, filters the packages that are normalized. +It is called with the package name as a string, and should return +non-nil if the package should actually be normalized. + +CONVERT-SNAPSHOTS non-nil (interactively, prefix arg) means if +repositories are snapshots, convert them to full repositories first. + +(fn &optional PREDICATE CONVERT-SNAPSHOTS)" t) +(autoload 'straight-fetch-package "straight" "\ +Try to fetch a PACKAGE from the primary remote. +PACKAGE is a string naming a package. Interactively, select +PACKAGE from the known packages in the current Emacs session +using `completing-read'. With prefix argument FROM-UPSTREAM, +fetch not just from primary remote but also from upstream (for +forked packages). + +(fn PACKAGE &optional FROM-UPSTREAM)" t) +(autoload 'straight-fetch-package-and-deps "straight" "\ +Try to fetch a PACKAGE and its (transitive) dependencies. +PACKAGE, its dependencies, their dependencies, etc. are fetched +from their primary remotes. + +PACKAGE is a string naming a package. Interactively, select +PACKAGE from the known packages in the current Emacs session +using `completing-read'. With prefix argument FROM-UPSTREAM, +fetch not just from primary remote but also from upstream (for +forked packages). + +(fn PACKAGE &optional FROM-UPSTREAM)" t) +(autoload 'straight-fetch-all "straight" "\ +Try to fetch all packages from their primary remotes. +With prefix argument FROM-UPSTREAM, fetch not just from primary +remotes but also from upstreams (for forked packages). + +Return a list of recipes for packages that were not successfully +fetched. If multiple packages come from the same local +repository, only one is fetched. + +PREDICATE, if provided, filters the packages that are fetched. It +is called with the package name as a string, and should return +non-nil if the package should actually be fetched. + +(fn &optional FROM-UPSTREAM PREDICATE)" t) +(autoload 'straight-merge-package "straight" "\ +Try to merge a PACKAGE from the primary remote. +PACKAGE is a string naming a package. Interactively, select +PACKAGE from the known packages in the current Emacs session +using `completing-read'. With prefix argument FROM-UPSTREAM, +merge not just from primary remote but also from upstream (for +forked packages). + +(fn PACKAGE &optional FROM-UPSTREAM)" t) +(autoload 'straight-merge-package-and-deps "straight" "\ +Try to merge a PACKAGE and its (transitive) dependencies. +PACKAGE, its dependencies, their dependencies, etc. are merged +from their primary remotes. + +PACKAGE is a string naming a package. Interactively, select +PACKAGE from the known packages in the current Emacs session +using `completing-read'. With prefix argument FROM-UPSTREAM, +merge not just from primary remote but also from upstream (for +forked packages). + +(fn PACKAGE &optional FROM-UPSTREAM)" t) +(autoload 'straight-merge-all "straight" "\ +Try to merge all packages from their primary remotes. +With prefix argument FROM-UPSTREAM, merge not just from primary +remotes but also from upstreams (for forked packages). + +Return a list of recipes for packages that were not successfully +merged. If multiple packages come from the same local +repository, only one is merged. + +PREDICATE, if provided, filters the packages that are merged. It +is called with the package name as a string, and should return +non-nil if the package should actually be merged. + +(fn &optional FROM-UPSTREAM PREDICATE)" t) +(autoload 'straight-pull-package "straight" "\ +Try to pull a PACKAGE from the primary remote. +PACKAGE is a string naming a package. Interactively, select +PACKAGE from the known packages in the current Emacs session +using `completing-read'. With prefix argument FROM-UPSTREAM, pull +not just from primary remote but also from upstream (for forked +packages). + +(fn PACKAGE &optional FROM-UPSTREAM)" t) +(autoload 'straight-pull-package-and-deps "straight" "\ +Try to pull a PACKAGE and its (transitive) dependencies. +PACKAGE, its dependencies, their dependencies, etc. are pulled +from their primary remotes. + +PACKAGE is a string naming a package. Interactively, select +PACKAGE from the known packages in the current Emacs session +using `completing-read'. With prefix argument FROM-UPSTREAM, +pull not just from primary remote but also from upstream (for +forked packages). + +(fn PACKAGE &optional FROM-UPSTREAM)" t) +(autoload 'straight-pull-all "straight" "\ +Try to pull all packages from their primary remotes. +With prefix argument FROM-UPSTREAM, pull not just from primary +remotes but also from upstreams (for forked packages). + +Return a list of recipes for packages that were not successfully +pulled. If multiple packages come from the same local repository, +only one is pulled. + +PREDICATE, if provided, filters the packages that are pulled. It +is called with the package name as a string, and should return +non-nil if the package should actually be pulled. + +(fn &optional FROM-UPSTREAM PREDICATE)" t) +(autoload 'straight-push-package "straight" "\ +Push a PACKAGE to its primary remote, if necessary. +PACKAGE is a string naming a package. Interactively, select +PACKAGE from the known packages in the current Emacs session +using `completing-read'. + +(fn PACKAGE)" t) +(autoload 'straight-push-all "straight" "\ +Try to push all packages to their primary remotes. + +Return a list of recipes for packages that were not successfully +pushed. If multiple packages come from the same local repository, +only one is pushed. + +PREDICATE, if provided, filters the packages that are normalized. +It is called with the package name as a string, and should return +non-nil if the package should actually be normalized. + +(fn &optional PREDICATE)" t) +(autoload 'straight-freeze-versions "straight" "\ +Write version lockfiles for currently activated packages. +This implies first pushing all packages that have unpushed local +changes. If the package management system has been used since the +last time the init-file was reloaded, offer to fix the situation +by reloading the init-file again. If FORCE is +non-nil (interactively, if a prefix argument is provided), skip +all checks and write the lockfile anyway. + +Currently, writing version lockfiles requires cloning all lazily +installed packages. Hopefully, this inconvenient requirement will +be removed in the future. + +Multiple lockfiles may be written (one for each profile), +according to the value of `straight-profiles'. + +(fn &optional FORCE)" t) +(autoload 'straight-thaw-versions "straight" "\ +Read version lockfiles and restore package versions to those listed." t) +(autoload 'straight-bug-report "straight" "\ +Test straight.el in a clean environment. +ARGS may be any of the following keywords and their respective values: + - :pre-bootstrap (Form)... + Forms evaluated before bootstrapping straight.el + e.g. (setq straight-repository-branch \"develop\") + Note this example is already in the default bootstrapping code. + + - :post-bootstrap (Form)... + Forms evaluated in the testing environment after boostrapping. + e.g. (straight-use-package \\='(example :type git :host github)) + + - :interactive Boolean + If nil, the subprocess will immediately exit after the test. + Output will be printed to `straight-bug-report--process-buffer' + Otherwise, the subprocess will be interactive. + + - :preserve Boolean + If non-nil, the test directory is left in the directory stored in the + variable `temporary-file-directory'. Otherwise, it is + immediately removed after the test is run. + + - :executable String + Indicate the Emacs executable to launch. + Defaults to the path of the current Emacs executable. + + - :raw Boolean + If non-nil, the raw process output is sent to + `straight-bug-report--process-buffer'. Otherwise, it is + formatted as markdown for submitting as an issue. + + - :user-dir String + If non-nil, the test is run with `user-emacs-directory' set to STRING. + Otherwise, a temporary directory is created and used. + Unless absolute, paths are expanded relative to the variable + `temporary-file-directory'. + +ARGS are accessible within the :pre/:post-bootsrap phases via the +locally bound plist, straight-bug-report-args. + +(fn &rest ARGS)" nil t) +(function-put 'straight-bug-report 'lisp-indent-function 0) +(autoload 'straight-dependencies "straight" "\ +Return a list of PACKAGE's dependencies, as strings. +PACKAGE is a string. If the dependencies have dependencies themselves, +then instead of strings they will be lists whose cars are the +dependencies and whose cdrs are the recursive dependencies in the same +format returned from `straight-dependencies'. + +Interactively, the user selects a package to show dependencies for, and +the dependencies are shown in the echo area. + +(fn &optional PACKAGE)" t) +(autoload 'straight-dependents "straight" "\ +Return a list of PACKAGE's dependents, as strings. +Dependents are packages that have the given package as a dependency. In +other words, this is the opposite of `straight-dependencies'. + +PACKAGE is a string. If the dependents have dependents themselves, then +instead of strings they will be lists whose cars are the dependents and +whose cdrs are the recursive dependents in the same format returned from +`straight-dependents'. + +(fn &optional PACKAGE)" t) +(register-definition-prefixes "straight" '("straight-")) + + +;;; Generated autoloads from straight-ert-print-hack.el + +(register-definition-prefixes "straight-ert-print-hack" '("+without-print-limits")) + + +;;; Generated autoloads from straight-x.el + +(defvar straight-x-pinned-packages nil "\ +List of pinned packages.") +(register-definition-prefixes "straight-x" '("straight-x-")) + +;;; End of scraped data + +(provide 'straight-autoloads) + +;; Local Variables: +;; version-control: never +;; no-byte-compile: t +;; no-update-autoloads: t +;; no-native-compile: t +;; coding: utf-8-emacs-unix +;; End: + +;;; straight-autoloads.el ends here diff --git a/straight/build/straight/straight-ert-print-hack.el b/straight/build/straight/straight-ert-print-hack.el new file mode 120000 index 0000000..25d02c3 --- /dev/null +++ b/straight/build/straight/straight-ert-print-hack.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/straight.el/straight-ert-print-hack.el
\ No newline at end of file diff --git a/straight/build/straight/straight-ert-print-hack.elc b/straight/build/straight/straight-ert-print-hack.elc Binary files differnew file mode 100644 index 0000000..ba1d012 --- /dev/null +++ b/straight/build/straight/straight-ert-print-hack.elc diff --git a/straight/build/straight/straight-x.el b/straight/build/straight/straight-x.el new file mode 120000 index 0000000..ea0ad68 --- /dev/null +++ b/straight/build/straight/straight-x.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/straight.el/straight-x.el
\ No newline at end of file diff --git a/straight/build/straight/straight-x.elc b/straight/build/straight/straight-x.elc Binary files differnew file mode 100644 index 0000000..59873f0 --- /dev/null +++ b/straight/build/straight/straight-x.elc diff --git a/straight/build/straight/straight.el b/straight/build/straight/straight.el new file mode 120000 index 0000000..6c2a30b --- /dev/null +++ b/straight/build/straight/straight.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/straight.el/straight.el
\ No newline at end of file diff --git a/straight/build/straight/straight.elc b/straight/build/straight/straight.elc Binary files differnew file mode 100644 index 0000000..59528c0 --- /dev/null +++ b/straight/build/straight/straight.elc diff --git a/straight/build/use-package/.github/PULL_REQUEST_TEMPLATE.md b/straight/build/use-package/.github/PULL_REQUEST_TEMPLATE.md new file mode 120000 index 0000000..ab8cbe4 --- /dev/null +++ b/straight/build/use-package/.github/PULL_REQUEST_TEMPLATE.md @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/use-package/.github/PULL_REQUEST_TEMPLATE.md
\ No newline at end of file diff --git a/straight/build/use-package/dir b/straight/build/use-package/dir new file mode 120000 index 0000000..9d95fe9 --- /dev/null +++ b/straight/build/use-package/dir @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/use-package/dir
\ No newline at end of file diff --git a/straight/build/use-package/doclicense.info b/straight/build/use-package/doclicense.info new file mode 100644 index 0000000..c8d7e71 --- /dev/null +++ b/straight/build/use-package/doclicense.info @@ -0,0 +1,488 @@ +This is doclicense.info, produced by makeinfo version 7.2 from +doclicense.texi. + + Version 1.3, 3 November 2008 + + Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. + <https://fsf.org/> + + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + 0. PREAMBLE + + The purpose of this License is to make a manual, textbook, or other + functional and useful document “free” in the sense of freedom: to + assure everyone the effective freedom to copy and redistribute it, + with or without modifying it, either commercially or + noncommercially. Secondarily, this License preserves for the + 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 + 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. + + We have designed this License in order to use it for manuals for + free software, because free software needs free documentation: a + free program should come with manuals providing the same freedoms + that the software does. But this License is not limited to + software manuals; it can be used for any textual work, regardless + of subject matter or whether it is published as a printed book. We + recommend this License principally for works whose purpose is + instruction or reference. + + 1. APPLICABILITY AND DEFINITIONS + + This License applies to any manual or other work, in any medium, + that contains a notice placed by the copyright holder saying it can + 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 + 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 + 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 + of the Document that deals exclusively with the relationship of the + 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 + explain any mathematics.) The relationship could be a matter of + historical connection with the subject or with related matters, or + of legal, commercial, philosophical, ethical or political position + regarding them. + + 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 + is not allowed to be designated as Invariant. The Document may + 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 + 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, + 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 + of pixels) generic paint programs or (for drawings) some widely + available drawing editor, and that is suitable for input to text + formatters or for automatic translation to a variety of formats + suitable for input to text formatters. A copy made in an otherwise + Transparent file format whose markup, or absence of markup, has + 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". + + Examples of suitable formats for Transparent copies include plain + ASCII without markup, Texinfo input format, LaTeX input format, + SGML or XML using a publicly available DTD, and standard-conforming + simple HTML, PostScript or PDF designed for human modification. + Examples of transparent image formats include PNG, XCF and JPG. + Opaque formats include proprietary formats that can be read and + edited only by proprietary word processors, SGML or XML for which + the DTD and/or processing tools are not generally available, and + 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, + 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. + + 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 + 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 + to this definition. + + The Document may include Warranty Disclaimers next to the notice + which states that this License applies to the Document. These + Warranty Disclaimers are considered to be included by reference in + this License, but only as regards disclaiming warranties: any other + implication that these Warranty Disclaimers may have is void and + has no effect on the meaning of this License. + + 2. VERBATIM COPYING + + You may copy and distribute the Document in any medium, either + commercially or noncommercially, provided that this License, the + copyright notices, and the license notice saying this License + applies to the Document are reproduced in all copies, and that you + add no other conditions whatsoever to those of this License. You + may not use technical measures to obstruct or control the reading + or further copying of the copies you make or distribute. However, + you may accept compensation in exchange for copies. If you + distribute a large enough number of copies you must also follow the + conditions in section 3. + + You may also lend copies, under the same conditions stated above, + and you may publicly display copies. + + 3. COPYING IN QUANTITY + + 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 + 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 + and legibly identify you as the publisher of these copies. The + front cover must present the full title with all words of the title + equally prominent and visible. You may add other material on the + covers in addition. Copying with changes limited to the covers, as + long as they preserve the title of the Document and satisfy these + conditions, can be treated as verbatim copying in other respects. + + If the required texts for either cover are too voluminous to fit + legibly, you should put the first ones listed (as many as fit + reasonably) on the actual cover, and continue the rest onto + adjacent pages. + + If you publish or distribute Opaque copies of the Document + numbering more than 100, you must either include a machine-readable + Transparent copy along with each Opaque copy, or state in or with + each Opaque copy a computer-network location from which the general + network-using public has access to download using public-standard + network protocols a complete Transparent copy of the Document, free + of added material. If you use the latter option, you must take + reasonably prudent steps, when you begin distribution of Opaque + copies in quantity, to ensure that this Transparent copy will + remain thus accessible at the stated location until at least one + year after the last time you distribute an Opaque copy (directly or + through your agents or retailers) of that edition to the public. + + It is requested, but not required, that you contact the authors of + the Document well before redistributing any large number of copies, + to give them a chance to provide you with an updated version of the + Document. + + 4. MODIFICATIONS + + You may copy and distribute a Modified Version of the Document + under the conditions of sections 2 and 3 above, provided that you + release the Modified Version under precisely this License, with the + Modified Version filling the role of the Document, thus licensing + distribution and modification of the Modified Version to whoever + possesses a copy of it. In addition, you must do these things in + the Modified Version: + + A. Use in the Title Page (and on the covers, if any) a title + distinct from that of the Document, and from those of previous + versions (which should, if there were any, be listed in the + History section of the Document). You may use the same title + as a previous version if the original publisher of that + version gives permission. + + B. List on the Title Page, as authors, one or more persons or + entities responsible for authorship of the modifications in + the Modified Version, together with at least five of the + principal authors of the Document (all of its principal + authors, if it has fewer than five), unless they release you + from this requirement. + + C. State on the Title page the name of the publisher of the + Modified Version, as the publisher. + + D. Preserve all the copyright notices of the Document. + + E. Add an appropriate copyright notice for your modifications + adjacent to the other copyright notices. + + F. Include, immediately after the copyright notices, a license + notice giving the public permission to use the Modified + Version under the terms of this License, in the form shown in + the Addendum below. + + G. Preserve in that license notice the full lists of Invariant + 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, + 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 + 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 + previous sentence. + + J. Preserve the network location, if any, given in the Document + 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 + 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", + 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. + + L. Preserve all the Invariant Sections of the Document, unaltered + 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 + 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 + Section. + + O. Preserve any Warranty Disclaimers. + + If the Modified Version includes new front-matter sections or + 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 + license notice. These titles must be distinct from any other + section titles. + + 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. + + 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 + the list of Cover Texts in the Modified Version. Only one passage + of Front-Cover Text and one of Back-Cover Text may be added by (or + through arrangements made by) any one entity. If the Document + already includes a cover text for the same cover, previously added + by you or by arrangement made by the same entity you are acting on + behalf of, you may not add another; but you may replace the old + one, on explicit permission from the previous publisher that added + the old one. + + The author(s) and publisher(s) of the Document do not by this + License give permission to use their names for publicity for or to + assert or imply endorsement of any Modified Version. + + 5. COMBINING DOCUMENTS + + You may combine the Document with other documents released under + this License, under the terms defined in section 4 above for + modified versions, provided that you include in the combination all + of the Invariant Sections of all of the original documents, + unmodified, and list them all as Invariant Sections of your + combined work in its license notice, and that you preserve all + their Warranty Disclaimers. + + The combined work need only contain one copy of this License, and + multiple identical Invariant Sections may be replaced with a single + copy. If there are multiple Invariant Sections with the same name + but different contents, make the title of each such section unique + by adding at the end of it, in parentheses, the name of the + original author or publisher of that section if known, or else a + unique number. Make the same adjustment to the section titles in + the list of Invariant Sections in the license notice of the + 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." + + 6. COLLECTIONS OF DOCUMENTS + + You may make a collection consisting of the Document and other + documents released under this License, and replace the individual + copies of this License in the various documents with a single copy + that is included in the collection, provided that you follow the + rules of this License for verbatim copying of each of the documents + in all other respects. + + You may extract a single document from such a collection, and + distribute it individually under this License, provided you insert + a copy of this License into the extracted document, and follow this + License in all other respects regarding verbatim copying of that + document. + + 7. AGGREGATION WITH INDEPENDENT WORKS + + 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 + copyright resulting from the compilation is not used to limit the + 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 + 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 + the whole aggregate. + + 8. TRANSLATION + + Translation is considered a kind of modification, so you may + distribute translations of the Document under the terms of section + 4. Replacing Invariant Sections with translations requires special + permission from their copyright holders, but you may include + translations of some or all Invariant Sections in addition to the + original versions of these Invariant Sections. You may include a + translation of this License, and all the license notices in the + Document, and any Warranty Disclaimers, provided that you also + include the original English version of this License and the + original versions of those notices and disclaimers. In case of a + disagreement between the translation and the original version of + 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 + Preserve its Title (section 1) will typically require changing the + actual title. + + 9. TERMINATION + + You may not copy, modify, sublicense, or distribute the Document + except as expressly provided under this License. Any attempt + otherwise to copy, modify, sublicense, or distribute it is void, + and will automatically terminate your rights under this License. + + However, if you cease all violation of this License, then your + license from a particular copyright holder is reinstated (a) + provisionally, unless and until the copyright holder explicitly and + finally terminates your license, and (b) permanently, if the + copyright holder fails to notify you of the violation by some + reasonable means prior to 60 days after the cessation. + + Moreover, your license from a particular copyright holder is + reinstated permanently if the copyright holder notifies you of the + violation by some reasonable means, this is the first time you have + received notice of violation of this License (for any work) from + that copyright holder, and you cure the violation prior to 30 days + after your receipt of the notice. + + Termination of your rights under this section does not terminate + the licenses of parties who have received copies or rights from you + under this License. If your rights have been terminated and not + permanently reinstated, receipt of a copy of some or all of the + same material does not give you any rights to use it. + + 10. FUTURE REVISIONS OF THIS LICENSE + + The Free Software Foundation may publish new, revised versions of + the GNU Free Documentation License from time to time. Such new + versions will be similar in spirit to the present version, but may + differ in detail to address new problems or concerns. See + <https://www.gnu.org/licenses/>. + + 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 + 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 + Document does not specify a version number of this License, you may + 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 + authorizes you to choose that version for the Document. + + 11. RELICENSING + + "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 + 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 + 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 + in part, as part of another Document. + + 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 + texts or invariant sections, and (2) were thus incorporated prior + to November 1, 2008. + + The operator of an MMC Site may republish an MMC contained in the + site under CC-BY-SA on the same site at any time before August 1, + 2009, provided the MMC is eligible for relicensing. + +ADDENDUM: How to use this License for your documents +==================================================== + +To use this License in a document you have written, include a copy of +the License in the document and put the following copyright and license +notices just after the title page: + + Copyright (C) YEAR YOUR NAME. + Permission is granted to copy, distribute and/or modify this 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, no Front-Cover Texts, and no Back-Cover + Texts. A copy of the license is included in the section entitled ``GNU + Free Documentation License''. + + If you have Invariant Sections, Front-Cover Texts and Back-Cover +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 + being LIST. + + If you have Invariant Sections without Cover Texts, or some other +combination of the three, merge those two alternatives to suit the +situation. + + If your document contains nontrivial examples of program code, we +recommend releasing these examples in parallel under your choice of free +software license, such as the GNU General Public License, to permit +their use in free software. + + +Tag Table: + +End Tag Table + + +Local Variables: +coding: utf-8 +End: diff --git a/straight/build/use-package/doclicense.texi b/straight/build/use-package/doclicense.texi new file mode 120000 index 0000000..ba8e92c --- /dev/null +++ b/straight/build/use-package/doclicense.texi @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/use-package/doclicense.texi
\ No newline at end of file diff --git a/straight/build/use-package/docstyle.info b/straight/build/use-package/docstyle.info new file mode 100644 index 0000000..600139c --- /dev/null +++ b/straight/build/use-package/docstyle.info @@ -0,0 +1,12 @@ +This is docstyle.info, produced by makeinfo version 7.2 from +docstyle.texi. + + +Tag Table: + +End Tag Table + + +Local Variables: +coding: utf-8 +End: diff --git a/straight/build/use-package/docstyle.texi b/straight/build/use-package/docstyle.texi new file mode 120000 index 0000000..365e3e5 --- /dev/null +++ b/straight/build/use-package/docstyle.texi @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/use-package/docstyle.texi
\ No newline at end of file diff --git a/straight/build/use-package/emacsver.info b/straight/build/use-package/emacsver.info new file mode 100644 index 0000000..21799eb --- /dev/null +++ b/straight/build/use-package/emacsver.info @@ -0,0 +1,12 @@ +This is emacsver.info, produced by makeinfo version 7.2 from +emacsver.texi. + + +Tag Table: + +End Tag Table + + +Local Variables: +coding: utf-8 +End: diff --git a/straight/build/use-package/emacsver.texi b/straight/build/use-package/emacsver.texi new file mode 120000 index 0000000..dab20c3 --- /dev/null +++ b/straight/build/use-package/emacsver.texi @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/use-package/emacsver.texi
\ No newline at end of file diff --git a/straight/build/use-package/use-package-autoloads.el b/straight/build/use-package/use-package-autoloads.el new file mode 100644 index 0000000..feec8c1 --- /dev/null +++ b/straight/build/use-package/use-package-autoloads.el @@ -0,0 +1,206 @@ +;;; use-package-autoloads.el --- automatically extracted autoloads (do not edit) -*- lexical-binding: t -*- +;; Generated by the `loaddefs-generate' function. + +;; This file is part of GNU Emacs. + +;;; Code: + + + +;;; Generated autoloads from use-package-bind-key.el + +(autoload 'use-package-autoload-keymap "use-package-bind-key" "\ +Load PACKAGE and bind key sequence invoking this function to KEYMAP-SYMBOL. +Then simulate pressing the same key sequence a again, so that the +next key pressed is routed to the newly loaded keymap. + +This function supports use-package's :bind-keymap keyword. It +works by binding the given key sequence to an invocation of this +function for a particular keymap. The keymap is expected to be +defined by the package. In this way, loading the package is +deferred until the prefix key sequence is pressed. + +(fn KEYMAP-SYMBOL PACKAGE OVERRIDE)") +(autoload 'use-package-normalize-binder "use-package-bind-key" "\ + + +(fn NAME KEYWORD ARGS)") +(defalias 'use-package-normalize/:bind 'use-package-normalize-binder) +(defalias 'use-package-normalize/:bind* 'use-package-normalize-binder) +(defalias 'use-package-autoloads/:bind 'use-package-autoloads-mode) +(defalias 'use-package-autoloads/:bind* 'use-package-autoloads-mode) +(autoload 'use-package-handler/:bind "use-package-bind-key" "\ + + +(fn NAME KEYWORD ARGS REST STATE &optional BIND-MACRO)") +(defalias 'use-package-normalize/:bind-keymap 'use-package-normalize-binder) +(defalias 'use-package-normalize/:bind-keymap* 'use-package-normalize-binder) +(autoload 'use-package-handler/:bind-keymap "use-package-bind-key" "\ + + +(fn NAME KEYWORD ARGS REST STATE &optional OVERRIDE)") +(autoload 'use-package-handler/:bind-keymap* "use-package-bind-key" "\ + + +(fn NAME KEYWORD ARG REST STATE)") +(register-definition-prefixes "use-package-bind-key" '("use-package-handler/:bind*")) + + +;;; Generated autoloads from use-package-core.el + +(autoload 'use-package "use-package-core" "\ +Declare an Emacs package by specifying a group of configuration options. + +For the full documentation, see Info node `(use-package) top'. +Usage: + + (use-package package-name + [:keyword [option]]...) + +:init Code to run before PACKAGE-NAME has been loaded. +:config Code to run after PACKAGE-NAME has been loaded. Note that + if loading is deferred for any reason, this code does not + execute until the lazy load has occurred. +:preface Code to be run before everything except `:disabled'; this + can be used to define functions for use in `:if', or that + should be seen by the byte-compiler. + +:mode Form to be added to `auto-mode-alist'. +:magic Form to be added to `magic-mode-alist'. +:magic-fallback Form to be added to `magic-fallback-mode-alist'. +:interpreter Form to be added to `interpreter-mode-alist'. + +:commands Define autoloads for commands defined by the package. + This is useful if the package is being lazily loaded, + and you wish to conditionally call functions in your + `:init' block that are defined in the package. +:autoload Similar to `:commands', but used for non-interactive functions. +:hook Specify hook(s) to attach this package to. + +:bind Bind keys, and define autoloads for the bound commands. +:bind* Bind keys, and define autoloads for the bound commands, + *overriding all minor mode bindings*. +:bind-keymap Bind a key prefix to an auto-loaded keymap defined in the + package. This is like `:bind', but for keymaps. +:bind-keymap* Like `:bind-keymap', but overrides all minor mode bindings + +:defer Defer loading of a package -- this is implied when using + `:commands', `:bind', `:bind*', `:mode', `:magic', `:hook', + `:magic-fallback', or `:interpreter'. This can be an integer, + to force loading after N seconds of idle time, if the package + has not already been loaded. +:demand Prevent the automatic deferred loading introduced by constructs + such as `:bind' (see `:defer' for the complete list). + +:after Delay the effect of the use-package declaration + until after the named libraries have loaded. + Before they have been loaded, no other keyword + has any effect at all, and once they have been + loaded it is as if `:after' was not specified. + +:if EXPR Initialize and load only if EXPR evaluates to a non-nil value. +:disabled The package is ignored completely if this keyword is present. +:defines Declare certain variables to silence the byte-compiler. +:functions Declare certain functions to silence the byte-compiler. +:load-path Add to the `load-path' before attempting to load the package. +:diminish Support for diminish.el (if installed). +:delight Support for delight.el (if installed). +:custom Call `customize-set-variable' on each variable + definition without modifying the Emacs `custom-file'. + (compare with `custom-set-variables'). +:custom-face Call `face-spec-set' with each face definition. +:ensure Loads the package using package.el if necessary. +:pin Pin the package to an archive. +:vc Install the package directly from a version control system + (using `package-vc.el'). + +(fn NAME &rest ARGS)" nil t) +(function-put 'use-package 'lisp-indent-function 'defun) +(register-definition-prefixes "use-package-core" '("use-package-")) + + +;;; Generated autoloads from use-package-delight.el + +(autoload 'use-package-normalize/:delight "use-package-delight" "\ +Normalize arguments to delight. + +(fn NAME KEYWORD ARGS)") +(autoload 'use-package-handler/:delight "use-package-delight" "\ + + +(fn NAME KEYWORD ARGS REST STATE)") +(register-definition-prefixes "use-package-delight" '("use-package-normalize-delight")) + + +;;; Generated autoloads from use-package-diminish.el + +(autoload 'use-package-normalize/:diminish "use-package-diminish" "\ + + +(fn NAME KEYWORD ARGS)") +(autoload 'use-package-handler/:diminish "use-package-diminish" "\ + + +(fn NAME KEYWORD ARG REST STATE)") +(register-definition-prefixes "use-package-diminish" '("use-package-normalize-diminish")) + + +;;; Generated autoloads from use-package-ensure.el + +(autoload 'use-package-normalize/:ensure "use-package-ensure" "\ + + +(fn NAME KEYWORD ARGS)") +(autoload 'use-package-handler/:ensure "use-package-ensure" "\ + + +(fn NAME KEYWORD ENSURE REST STATE)") +(register-definition-prefixes "use-package-ensure" '("use-package-")) + + +;;; Generated autoloads from use-package-ensure-system-package.el + +(autoload 'use-package-normalize/:ensure-system-package "use-package-ensure-system-package" "\ +Turn ARGS into a list of conses of the form (PACKAGE-NAME . INSTALL-COMMAND). + +(fn NAME-SYMBOL KEYWORD ARGS)") +(autoload 'use-package-handler/:ensure-system-package "use-package-ensure-system-package" "\ +Execute the handler for `:ensure-system-package' keyword in `use-package'. + +(fn NAME KEYWORD ARG REST STATE)") +(register-definition-prefixes "use-package-ensure-system-package" '("use-package-ensure-system-package-")) + + +;;; Generated autoloads from use-package-jump.el + +(autoload 'use-package-jump-to-package-form "use-package-jump" "\ +Attempt to find and jump to the `use-package' form that loaded PACKAGE. +This will only find the form if that form actually required +PACKAGE. If PACKAGE was previously required then this function +will jump to the file that originally required PACKAGE instead. + +(fn PACKAGE)" t) +(register-definition-prefixes "use-package-jump" '("use-package-find-require")) + + +;;; Generated autoloads from use-package-lint.el + +(autoload 'use-package-lint "use-package-lint" "\ +Check for errors in `use-package' declarations. +For example, if the module's `:if' condition is met, but even +with the specified `:load-path' the module cannot be found." t) +(register-definition-prefixes "use-package-lint" '("use-package-lint-declaration")) + +;;; End of scraped data + +(provide 'use-package-autoloads) + +;; Local Variables: +;; version-control: never +;; no-byte-compile: t +;; no-update-autoloads: t +;; no-native-compile: t +;; coding: utf-8-emacs-unix +;; End: + +;;; use-package-autoloads.el ends here diff --git a/straight/build/use-package/use-package-bind-key.el b/straight/build/use-package/use-package-bind-key.el new file mode 120000 index 0000000..eef114c --- /dev/null +++ b/straight/build/use-package/use-package-bind-key.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/use-package/use-package-bind-key.el
\ No newline at end of file diff --git a/straight/build/use-package/use-package-bind-key.elc b/straight/build/use-package/use-package-bind-key.elc Binary files differnew file mode 100644 index 0000000..30f8ff2 --- /dev/null +++ b/straight/build/use-package/use-package-bind-key.elc diff --git a/straight/build/use-package/use-package-core.el b/straight/build/use-package/use-package-core.el new file mode 120000 index 0000000..823b9cc --- /dev/null +++ b/straight/build/use-package/use-package-core.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/use-package/use-package-core.el
\ No newline at end of file diff --git a/straight/build/use-package/use-package-core.elc b/straight/build/use-package/use-package-core.elc Binary files differnew file mode 100644 index 0000000..bedc939 --- /dev/null +++ b/straight/build/use-package/use-package-core.elc diff --git a/straight/build/use-package/use-package-delight.el b/straight/build/use-package/use-package-delight.el new file mode 120000 index 0000000..3a34ec5 --- /dev/null +++ b/straight/build/use-package/use-package-delight.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/use-package/use-package-delight.el
\ No newline at end of file diff --git a/straight/build/use-package/use-package-delight.elc b/straight/build/use-package/use-package-delight.elc Binary files differnew file mode 100644 index 0000000..767ca8d --- /dev/null +++ b/straight/build/use-package/use-package-delight.elc diff --git a/straight/build/use-package/use-package-diminish.el b/straight/build/use-package/use-package-diminish.el new file mode 120000 index 0000000..12fda02 --- /dev/null +++ b/straight/build/use-package/use-package-diminish.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/use-package/use-package-diminish.el
\ No newline at end of file diff --git a/straight/build/use-package/use-package-diminish.elc b/straight/build/use-package/use-package-diminish.elc Binary files differnew file mode 100644 index 0000000..208912e --- /dev/null +++ b/straight/build/use-package/use-package-diminish.elc diff --git a/straight/build/use-package/use-package-ensure-system-package.el b/straight/build/use-package/use-package-ensure-system-package.el new file mode 120000 index 0000000..5568d5b --- /dev/null +++ b/straight/build/use-package/use-package-ensure-system-package.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/use-package/use-package-ensure-system-package.el
\ No newline at end of file diff --git a/straight/build/use-package/use-package-ensure-system-package.elc b/straight/build/use-package/use-package-ensure-system-package.elc Binary files differnew file mode 100644 index 0000000..c1ee66d --- /dev/null +++ b/straight/build/use-package/use-package-ensure-system-package.elc diff --git a/straight/build/use-package/use-package-ensure.el b/straight/build/use-package/use-package-ensure.el new file mode 120000 index 0000000..9fb4702 --- /dev/null +++ b/straight/build/use-package/use-package-ensure.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/use-package/use-package-ensure.el
\ No newline at end of file diff --git a/straight/build/use-package/use-package-ensure.elc b/straight/build/use-package/use-package-ensure.elc Binary files differnew file mode 100644 index 0000000..65f006f --- /dev/null +++ b/straight/build/use-package/use-package-ensure.elc diff --git a/straight/build/use-package/use-package-jump.el b/straight/build/use-package/use-package-jump.el new file mode 120000 index 0000000..9fc7b5b --- /dev/null +++ b/straight/build/use-package/use-package-jump.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/use-package/use-package-jump.el
\ No newline at end of file diff --git a/straight/build/use-package/use-package-jump.elc b/straight/build/use-package/use-package-jump.elc Binary files differnew file mode 100644 index 0000000..112016d --- /dev/null +++ b/straight/build/use-package/use-package-jump.elc diff --git a/straight/build/use-package/use-package-lint.el b/straight/build/use-package/use-package-lint.el new file mode 120000 index 0000000..b192667 --- /dev/null +++ b/straight/build/use-package/use-package-lint.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/use-package/use-package-lint.el
\ No newline at end of file diff --git a/straight/build/use-package/use-package-lint.elc b/straight/build/use-package/use-package-lint.elc Binary files differnew file mode 100644 index 0000000..c9fc593 --- /dev/null +++ b/straight/build/use-package/use-package-lint.elc diff --git a/straight/build/use-package/use-package-pkg.el b/straight/build/use-package/use-package-pkg.el new file mode 120000 index 0000000..c8c78b7 --- /dev/null +++ b/straight/build/use-package/use-package-pkg.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/use-package/use-package-pkg.el
\ No newline at end of file diff --git a/straight/build/use-package/use-package.el b/straight/build/use-package/use-package.el new file mode 120000 index 0000000..8bfa511 --- /dev/null +++ b/straight/build/use-package/use-package.el @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/use-package/use-package.el
\ No newline at end of file diff --git a/straight/build/use-package/use-package.elc b/straight/build/use-package/use-package.elc Binary files differnew file mode 100644 index 0000000..099d405 --- /dev/null +++ b/straight/build/use-package/use-package.elc diff --git a/straight/build/use-package/use-package.info b/straight/build/use-package/use-package.info new file mode 120000 index 0000000..a4d3ab4 --- /dev/null +++ b/straight/build/use-package/use-package.info @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/use-package/use-package.info
\ No newline at end of file diff --git a/straight/build/use-package/use-package.texi b/straight/build/use-package/use-package.texi new file mode 120000 index 0000000..a0c981c --- /dev/null +++ b/straight/build/use-package/use-package.texi @@ -0,0 +1 @@ +/home/bh/.config/emacs/straight/repos/use-package/use-package.texi
\ No newline at end of file |