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