October 2014 - implementations-list

visual selection and X primary behavior
by Linus Arver 27 Jan '15

27 Jan '15

Hello all, In regular Emacs (with Evil mode turned on, of course), I can (1) do visual selection of a region, and it will automatically copy that selection into the X primary selection buffer. This way, I can simply do SHIFT+INSERT in another X program (e.g., Firefox) and I will paste the selection that way. Conversely, I can (2) SHIFT+INSERT into Emacs/Evil (in Insert mode), and it will paste whatever is in the X primary buffer. However, behavior (1) does not work in terminal-mode Emacs (`emacs -nw`), although behavior (2) works as expected. I have tried to work around this by using my `"+y` macro which is enabled with (define-key evil-normal-state-map ",y" "\"+y") in my .emacs, but it fails with the message After 0 kbd macro iterations: X selection unavailable for this frame . Is this a bug in Evil or is it something in Emacs itself? -L

3 8

[Bug?] Evil does not activate when loaded via customize
by Trevor Murphy 03 Nov '14

03 Nov '14

Hi, list! I'm perverse and want to install Evil via package.el and load it via customize. I notice that Evil does not turn on at startup when I customize evil-mode to t. I still have to explicitly call (evil-mode 1) in my init-file. Is this known behavior? If so, is it a bug? If so, can I fix it somehow? Note: I know the documentation explicitly tells me to install Evil like so: (add-to-list 'load-path "~/.emacs.d/evil") (require 'evil) (evil-mode 1) As said, I'm just being perverse. Thanks for any pointers! -- Trevor Murphy, ASA, MAAA GnuPG Key: 0x83881C0A

2 5

T, t, F, f operators crash into debugger
by David Nebauer 21 Oct '14

21 Oct '14

When vim operators T, t, F and f fail in vim because the target cannot be found, it triggers an error which sounds a bell, but otherwise does not interrupt editing. In evil, on the other hand, when T, T, F and f operators fail in evil they cause the debugger to open in another buffer with the lisp error "Can't find X" where X is the target character. To an emacs/evil newcomer like me it seems a predictable error like this should not cause code execution to crash and invoke the debugger. My naive suggestion would be that it should indicate an error (perhaps using the system bell or returning an error message in the minibuffer) but continue running without crashing in to the debugger. I accept that it takes only the press of the 'q' button to close the debugger and return to editing. Nonetheless, that is one button more than vim. Further, because I associate the debugger with a program crash, every time T, t, F or f fail in evil I am briefly jarred out of my editing mindset. Is there any way to prevent a failed F, f, T or t operation from crashing and invoking the debugger?

4 5

tildes + helm integration
by Jabba Laci 19 Oct '14

19 Oct '14

Hi, I'm new to the list and Evil. In the past 3 days I could customize lots of things. I would have 2 questions: 1) Is there a way to show blue tildes (~) after the last line of a file? I miss that feature. 2) I installed the Helm plugin but it stole some key bindings that I'm used to. For instance, "gf" in Evil opens the file under the cursor, while "gf" in Helm means "find a file". So I uncommented Helm in my config file, but I'd like to use it. Do you have a solution how to prevent it from stealing key bindings? In my config file I also changed the order of imports (first Helm then Evil, then vice versa) but it didn't help. Thanks, Laszlo

1 0

Re: Search for selected text
by David Nebauer 15 Oct '14

15 Oct '14

> (define-key evil-ex-search-keymap "\C-r" 'evil-paste-from-register) > (define-key evil-visual-state-map "/" "y/\C-r\"\C-m") Thanks for the prompt answer. This solution provides precisely the same functionality as vim. Please keep up the excellent work. Regards, David.

1 0

Search for selected text
by David Nebauer 14 Oct '14

14 Oct '14

There are a couple of handy shortcuts in vim that allow you to highlight text and then hit '/' or '?' to search forwards or backwards for the next occurrence of the selected text. The mappings are: vnoremap / y/<C-R>"<CR> vnoremap ? y?<C-R>"<CR> Is there any way to replicate this functionality in evil?

3 2

Mapping ( and ) in paredit mode
by Nikolai Weibull 01 Oct '14

01 Oct '14

Hi! I would like to map ( and ) as prefix keys to various other mappings to paredit mode functions: (evil-define-key 'normal paredit-mode-map "((" 'evil-paredit-backward-slurp-sexp "))" 'evil-paredit-forward-slurp-sexp ...) This only works after a while for inexplicable reasons when you’ve clicked around a bit and tried to execute a couple of mappings in a buffer with Paredit enabled. The problem is that ( is mapped to backward-sentence in evil-motion-state-map, which seems to take precedence. How do I go about removing the mapping of ( to backward-sentence in evil-motion-state-map for buffers that have Paredit enabled? (I’m sure that this worked without any issues before, but I’ve changed my configuration somewhat and now I get this weird behavior.) Oh, using (define-key evil-normal-state-local-map "((" 'evil-paredit-backward-slurp-sexp) seems to work. So is that the preferred way of solving this situation?

2 5