| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
fixes #1595
|
|
In visual state, it restores point to beginning of visual range
Fixes #1593
|
|
|
|
fixes #883
|
|
|
|
* evil-ex.el (evil-ex-grammar): Handle ] and [ registers
Co-authored-by: Brian Leung <leungbk@posteo.net>
Co-authored-by: Tom Dalziel <tom_dl@hotmail.com>
* evil-ex (evil-ex-grammar): Handle more range types
* evil-ex.el (evil-ex-grammar): Handle comma- or semicolon-separated
ranges that omit the first argument. The current line will be used as
the input.
Co-authored-by: Brian Leung <leungbk@posteo.net>
Co-authored-by: Nathaniel Nicandro <nathanielnicandro@gmail.com>
Co-authored-by: Tom Dalziel <tom_dl@hotmail.com>
|
|
Fixes #1551
|
|
|
|
|
|
* Add wraparound to `evil-ex-re-fwd` + `evil-ex-re-bwd`
Fixes a bug noted in #1482
* Tests for 1482
|
|
* Introduce `evil-paste-clear-minibuffer-first` to aid `C-r` on search
* Add test for pasting from register in ex-search prompt
|
|
The latest Emacs 28 requires this.
|
|
|
|
|
|
|
|
This reverts commit e9391ae769bee189ef6144b8861b117d5c948a80, and
removes spurious debug messages.
|
|
This reverts commit c6086a7b0b44963071096e3ed7545f617de88915.
|
|
|
|
Open apropriate command windows for Ctrl-f while in minibuffer for an ex command
or a search. As all ways to abort a minibuffer do not return and restore the
active buffer, we have to set the content of the minibuffer and exit normally to
trigger the apropriate action. Also restoring the window configuration is
necessary so minibuffer-selected-window is not changed.
|
|
|
|
Version 1.2.15 was accidentally tagged as 1.12.15, and released as
such by MELPA Stable, so now I guess we have to run with it.
|
|
|
|
|
|
This triggers ex command completion even outside of the command
syntactical context. To compensate, the completion now falls through
to argument context if no commands can be found.
|
|
Fixes #1202
|
|
Closes #919
|
|
|
|
|
|
|
|
When `enable-recursive-minibuffers` is non-nil it is
possible to enter another minibuffer at a lower editing
depth from within the Ex minibuffer.
Since `evil-ex-teardown` is added to the global value of
`minibuffer-exit-hook`, it will only be called in the
minibuffer at the lower level when it exits instead of in
the Ex minibuffer since it is removed from
`minibuffer-exit-hook` when it is called.
But this means that `evil-ex-update` will not be properly
cleaned up since it is added to the local value of
`after-change-functions` in the Ex minibuffer.
After completely exiting all minibuffers and then entering a
minibuffer that is not an Ex minibuffer, `evil-ex-update`
will still be in `after-change-functions` due to how
minibuffers are
named (https://www.gnu.org/software/emacs/manual/html_node/elisp/Intro-to-Minibuffers.html)
and assuming that the initial Ex was entered when the
recursive editing depth was 0.
Instead of adding `evil-ex-teardown` to the global value of
`minibuffer-exit-hook`, this commit adds it to the local
value of `minibuffer-exit-hook` in the Ex minibuffer so that
`evil-ex-update` is properly removed regardless of how many
recursive minibuffers there are.
|
|
|
|
|
|
As a result, when the following code is executed from lisp, the
substitution overlays will be displayed `(evil-ex "%s/this/that")`
|
|
|
|
|
|
|
|
Now that `shell' has been required at the top level, we don't need to require it
inside any functions in the same file. To calm down byte compiler, `require'
statements have to be placed outside of any function because they are not parsed
at compile time if they are inside functions.
|
|
|
|
Closes #729
|
|
|
|
|
|
* run pre/post-command-hook before and after calling the command,
resp.
* set `this-command` appropriately
* required for the jump system to work because it relies on hooks
|
|
|
|
|
|
|
|
|
|
Avoid checking (commandp binding) twice in a row
|
|
In evil-ex-binding, check for remaps before returning final
command.
|
