| Age | Commit message (Collapse) | Author |
|---|
|
Release 1.12.17
|
|
|
|
When setting a new global map, the tab-bar entry must be copied to the new
map from the old one to avoid hiding the tab bar.
* evil-common.el (evil-read-key): Preserve the tab-bar entry from the old
global map.
|
|
|
|
Release 1.12.16 (Oops)
|
|
1.2.15 was accidentally tagged as 1.12.15, which was picked up and
released by MELPA Stable. So to be able to release new stable
versions I guess it's easiest to just say that we're on 1.12 now.
|
|
Release 1.2.16
|
|
|
|
|
|
"A FILE with an "ext:" prefix is an external file.
check-declare will check such files if they are found, and skip
them without error if they are not."
|
|
|
|
Support to toggling in vdiff-3way-mode
|
|
Handle empty buffer when shifting left/right
|
|
Closes #930
|
|
Fix behavior of evil-scroll-up and evil-scroll-down
|
|
|
|
|
|
|
|
enabled
|
|
Some modes, like fzf.el, will put :fzf-windows as register name,
causing Evil :register command to fail. This command, but also Vim,
expects registers to be named with number or character.
This commit fixes it by filtering out all register names not conforming to
proper Vim-like naming schema.
|
|
Add evil-send-leader and evil-send-localleader which will push the symbol
<leader> or <localleader> into the unread-command-events list. This allows one
to bind a key to evil-send-leader to make it a leader key and activate bindings
like the following.
(defun hi ()
(interactive)
(message "hi"))
(define-key evil-normal-state-map (kbd "<leader> h") 'hi)
For convenience, evil-set-leader can be used as follows
(evil-set-leader 'normal (kbd "C-c"))
An optional argument makes it a localleader.
|
|
Fixes #1206
|
|
Some more advanced backends require this to work.
|
|
|
|
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
|
|
|
|
Docstring says that the spec can be a zero-argument function, but
evil-set-cursor incorrectly handles such a function like a list preventing the
function from being executed.
|
|
Closes #939
|
|
|
|
Closes #919
|
|
|
|
See https://debbugs.gnu.org/cgi/bugreport.cgi?bug=31546
|
|
|
|
|
|
|
|
|
|
|
|
Also wrap the 'make test' invocation within 'script', hiding all the
messy TTY output on the Travis logs.
|
|
Instead, run tests using ert-run-tests-interactively, save the buffer
to a text file and then exit using kill-emacs.
|
|
Make evil-yank aware of screen-lines
|
|
when evil-respect-visual-line-mode is non-nil, including
evil-change-line, evil-delete-line, and evil-yank-line. Most of the work is done
through the motions evil-line-or-visual-line and
evil-end-of-line-or-visual-line. These motions use visual lines when
visual-line-mode and evil-respect-visual-line-mode are non-nil, and revert back
to standard lines otherwise.
Visual selection via visual lines in the sense of visual-line-mode is supported
by adding a new screen-line type (named to avoid confusion with visual state).
|
|
The conditions checked in the body of the function are sufficient to guarantee
that the cursor should move back so there is no need to check the variable
evil-move-cursor-back, which is what the force argument allows for.
|
|
The docstring of evil-cursor-back only mentions that it applies to moving the
cursor back when exiting insert state, but in many cases it was tied to also
moving the cursor when reaching the end of the line. We have
evil-move-beyond-eol to control that behavior, and there doesn't seem to be a
good reason that the two must be tied together.
Fixes #1178
|
|
If evil-jump-backward-swap gets called (for the ` and ' marks) and
switches the current buffer, evil-get-marker won't restore the buffer.
|
|
|
|
|
|
|
|
Windows created specifically to hold evil-list-view-mode buffers seem a lot like
other temporary windows in Emacs, e.g. the ones created by describe-function.
These tend to define q to mean quit-window, rather than kill-this-buffer; The
quit-window command has the nice property that if a window was created to hold
the buffer in question, that window will be deleted – but if an existing window
was repurposed to hold the buffer, the effect is the same as bury-buffer.
Note that this is also in line with the default behaviour of Vim, where pressing
q in the marks list restores the previous window layout.
|
|
On Emacs latest the test is broken somehow. (The feature works fine
but the test not.)
|
