79 lines
3.2 KiB
EmacsLisp
79 lines
3.2 KiB
EmacsLisp
;;; evil-collection-autoloads.el --- automatically extracted autoloads -*- lexical-binding: t -*-
|
||
;;
|
||
;;; Code:
|
||
|
||
|
||
;;;### (autoloads nil "evil-collection" "evil-collection.el" (0 0
|
||
;;;;;; 0 0))
|
||
;;; Generated autoloads from evil-collection.el
|
||
|
||
(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)" nil nil)
|
||
|
||
(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-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)" nil nil)
|
||
|
||
(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 nil)
|
||
|
||
(register-definition-prefixes "evil-collection" '("evil-collection-"))
|
||
|
||
;;;***
|
||
|
||
(provide 'evil-collection-autoloads)
|
||
;; Local Variables:
|
||
;; version-control: never
|
||
;; no-byte-compile: t
|
||
;; no-update-autoloads: t
|
||
;; coding: utf-8
|
||
;; End:
|
||
;;; evil-collection-autoloads.el ends here
|