Fox Kiester

Now that it's in melpa, I will add a `:repeater` keyword. Based on the syntax, I was under the mistaken impression that it would support a variable for the first...

I don't think that it is much of an issue for `defrepeater` to use `eval` for this. One of us has to use `eval` with `defrepeater` in its current form....

> should use syntax like defalias Well `defalias` does normally use `fset`. For example, this works: ```elisp (defvar var #'foo) (defalias var #'+) (foo 1 2) ;; => 3 ```...

Actually, you're correct about `defrepeater` using `eval`; my bad. You can't rely on argument values during macro expansion. You can if the variables are defined at expansion time, but that's...

I've added experimental (no tests) support for automatic unbinding. You can call `(general-auto-unbind-keys)` if you want to try it. Since general doesn't necessarily know the keymap the key will end...

For normal keyword arguments, specifying them twice will override values. Use-package does have its own custom handling of keyword arguments, but are there other keyword arguments that can be specified...

The initial example should be `:keymaps 'override :states 'normal`. Currently the override keymaps are only set to override evil for the exact state specified, so unless you are actually in...

Normally keybindings made in motion state are inherited in other states. Keybindings made in normal state are inherited by other states as well excluding motion state, so unless you want...

> I was under the impression that evil designated that mode for some buffers. Yes, by default various read-only buffers default to motion state (see `evil-motion-state-modes`), but this is easily...

`general-override-mode` is now automatically enabled by default since most people probably won't want to toggle it off later. As for your second point, if you think that the documentation for...