embark-autoloads.el (8879B)
1 ;;; embark-autoloads.el --- automatically extracted autoloads (do not edit) -*- lexical-binding: t -*- 2 ;; Generated by the `loaddefs-generate' function. 3 4 ;; This file is part of GNU Emacs. 5 6 ;;; Code: 7 8 (add-to-list 'load-path (or (and load-file-name (directory-file-name (file-name-directory load-file-name))) (car load-path))) 9 10 11 12 ;;; Generated autoloads from embark.el 13 14 (defun embark--record-this-command nil "\ 15 Record command which opened the minibuffer. 16 We record this because it will be the default action. 17 This function is meant to be added to `minibuffer-setup-hook'." (setq-local embark--command this-command)) 18 (add-hook 'minibuffer-setup-hook #'embark--record-this-command) 19 (autoload 'embark-eldoc-first-target "embark" "\ 20 Eldoc function reporting the first Embark target at point. 21 This function uses the eldoc REPORT callback and is meant to be 22 added to `eldoc-documentation-functions'. 23 24 (fn REPORT &rest _)") 25 (autoload 'embark-eldoc-target-types "embark" "\ 26 Eldoc function reporting the types of all Embark targets at point. 27 This function uses the eldoc REPORT callback and is meant to be 28 added to `eldoc-documentation-functions'. 29 30 (fn REPORT &rest _)") 31 (autoload 'embark-bindings-in-keymap "embark" "\ 32 Explore command key bindings in KEYMAP with `completing-read'. 33 The selected command will be executed. Interactively, prompt the 34 user for a KEYMAP variable. 35 36 (fn KEYMAP)" t) 37 (autoload 'embark-bindings "embark" "\ 38 Explore current command key bindings with `completing-read'. 39 The selected command will be executed. 40 41 This shows key bindings from minor mode maps and the local 42 map (usually set by the major mode), but also less common keymaps 43 such as those from a text property or overlay, or the overriding 44 maps: `overriding-terminal-local-map' and `overriding-local-map'. 45 46 Additionally, if GLOBAL is non-nil (interactively, if called with 47 a prefix argument), this command includes global key bindings. 48 49 (fn GLOBAL)" t) 50 (autoload 'embark-bindings-at-point "embark" "\ 51 Explore all key bindings at point with `completing-read'. 52 The selected command will be executed. 53 54 This command lists key bindings found in keymaps specified by the 55 text properties `keymap' or `local-map', from either buffer text 56 or an overlay. These are not widely used in Emacs, and when they 57 are used can be somewhat hard to discover. Examples of locations 58 that have such a keymap are links and images in `eww' buffers, 59 attachment links in `gnus' article buffers, and the stash line 60 in a `vc-dir' buffer." t) 61 (autoload 'embark-prefix-help-command "embark" "\ 62 Prompt for and run a command bound in the prefix used for this command. 63 The prefix described consists of all but the last event of the 64 key sequence that ran this command. This function is intended to 65 be used as a value for `prefix-help-command'. 66 67 In addition to using completion to select a command, you can also 68 type @ and the key binding (without the prefix)." t) 69 (autoload 'embark-act "embark" "\ 70 Prompt the user for an action and perform it. 71 The targets of the action are chosen by `embark-target-finders'. 72 By default, if called from a minibuffer the target is the top 73 completion candidate. When called from a non-minibuffer buffer 74 there can multiple targets and you can cycle among them by using 75 `embark-cycle' (which is bound by default to the same key 76 binding `embark-act' is, but see `embark-cycle-key'). 77 78 This command uses `embark-prompter' to ask the user to specify an 79 action, and calls it injecting the target at the first minibuffer 80 prompt. 81 82 If you call this from the minibuffer, it can optionally quit the 83 minibuffer. The variable `embark-quit-after-action' controls 84 whether calling `embark-act' with nil ARG quits the minibuffer, 85 and if ARG is non-nil it will do the opposite. Interactively, 86 ARG is the prefix argument. 87 88 If instead you call this from outside the minibuffer, the first 89 ARG targets are skipped over (if ARG is negative the skipping is 90 done by cycling backwards) and cycling starts from the following 91 target. 92 93 (fn &optional ARG)" t) 94 (autoload 'embark-act-all "embark" "\ 95 Prompt the user for an action and perform it on each candidate. 96 The candidates are chosen by `embark-candidate-collectors'. By 97 default, if `embark-select' has been used to select some 98 candidates, then `embark-act-all' will act on those candidates; 99 otherwise, if the selection is empty and `embark-act-all' is 100 called from a minibuffer, then the candidates are the completion 101 candidates. 102 103 This command uses `embark-prompter' to ask the user to specify an 104 action, and calls it injecting the target at the first minibuffer 105 prompt. 106 107 If you call this from the minibuffer, it can optionally quit the 108 minibuffer. The variable `embark-quit-after-action' controls 109 whether calling `embark-act' with nil ARG quits the minibuffer, 110 and if ARG is non-nil it will do the opposite. Interactively, 111 ARG is the prefix argument. 112 113 (fn &optional ARG)" t) 114 (autoload 'embark-dwim "embark" "\ 115 Run the default action on the current target. 116 The target of the action is chosen by `embark-target-finders'. 117 118 If the target comes from minibuffer completion, then the default 119 action is the command that opened the minibuffer in the first 120 place, unless overridden by `embark-default-action-overrides'. 121 122 For targets that do not come from minibuffer completion 123 (typically some thing at point in a regular buffer) and whose 124 type is not listed in `embark-default-action-overrides', the 125 default action is given by whatever binding RET has in the action 126 keymap for the target's type. 127 128 See `embark-act' for the meaning of the prefix ARG. 129 130 (fn &optional ARG)" t) 131 (autoload 'embark-become "embark" "\ 132 Make current command become a different command. 133 Take the current minibuffer input as initial input for new 134 command. The new command can be run normally using key bindings or 135 \\[execute-extended-command], but if the current command is found in a keymap in 136 `embark-become-keymaps', that keymap is activated to provide 137 convenient access to the other commands in it. 138 139 If FULL is non-nil (interactively, if called with a prefix 140 argument), the entire minibuffer contents are used as the initial 141 input of the new command. By default only the part of the 142 minibuffer contents between the current completion boundaries is 143 taken. What this means is fairly technical, but (1) usually 144 there is no difference: the completion boundaries include the 145 entire minibuffer contents, and (2) the most common case where 146 these notions differ is file completion, in which case the 147 completion boundaries single out the path component containing 148 point. 149 150 (fn &optional FULL)" t) 151 (autoload 'embark-collect "embark" "\ 152 Create an Embark Collect buffer. 153 154 To control the display, add an entry to `display-buffer-alist' 155 with key \"Embark Collect\". 156 157 In Embark Collect buffers `revert-buffer' is remapped to 158 `embark-rerun-collect-or-export', which has slightly unusual 159 behavior if the buffer was obtained by running `embark-collect' 160 from within a minibuffer completion session. In that case 161 rerunning just restarts the completion session, that is, the 162 command that opened the minibuffer is run again and the 163 minibuffer contents restored. You can then interact normally with 164 the command, perhaps editing the minibuffer contents, and, if you 165 wish, you can rerun `embark-collect' to get an updated buffer." t) 166 (autoload 'embark-live "embark" "\ 167 Create a live-updating Embark Collect buffer. 168 169 To control the display, add an entry to `display-buffer-alist' 170 with key \"Embark Live\"." t) 171 (autoload 'embark-export "embark" "\ 172 Create a type-specific buffer to manage current candidates. 173 The variable `embark-exporters-alist' controls how to make the 174 buffer for each type of completion. 175 176 In Embark Export buffers `revert-buffer' is remapped to 177 `embark-rerun-collect-or-export', which has slightly unusual 178 behavior if the buffer was obtained by running `embark-export' 179 from within a minibuffer completion session. In that case 180 reverting just restarts the completion session, that is, the 181 command that opened the minibuffer is run again and the 182 minibuffer contents restored. You can then interact normally 183 with the command, perhaps editing the minibuffer contents, and, 184 if you wish, you can rerun `embark-export' to get an updated 185 buffer." t) 186 (autoload 'embark-select "embark" "\ 187 Add or remove the target from the current buffer's selection. 188 You can act on all selected targets at once with `embark-act-all'. 189 When called from outside `embark-act' this command will select 190 the first target at point." t) 191 (register-definition-prefixes "embark" '("embark-")) 192 193 194 ;;; Generated autoloads from embark-org.el 195 196 (register-definition-prefixes "embark-org" '("embark-org-")) 197 198 199 ;;; End of scraped data 200 201 (provide 'embark-autoloads) 202 203 ;; Local Variables: 204 ;; version-control: never 205 ;; no-byte-compile: t 206 ;; no-update-autoloads: t 207 ;; no-native-compile: t 208 ;; coding: utf-8-emacs-unix 209 ;; End: 210 211 ;;; embark-autoloads.el ends here