January 2013 - implementations-list

<backspace> not bound properly in haskell-mode
by Keshav Kini 25 Jul '14

25 Jul '14

When I have a .hs file open in a buffer (i.e. with haskell-mode activated), it seems that typing <backspace> in <N> state actually deletes characters. Investigating a bit, I see that in other modes - such as message-mode, in which I'm typing this email - doing describe-key on <backspace> yields the following: DEL (translated from <backspace>) runs the command evil-backward-char, which is an interactive compiled Lisp function in `evil-commands.el'. In haskell-mode, however, I get: <backspace> runs the command haskell-indentation-delete-backward-char, which is an interactive compiled Lisp function in `haskell-indentation.el'. The difference I notice is that in the first, we have "DEL (translated from <backspace>)", but in the second, just "<backspace>". From this I gather that evil-mode probably traps the key DEL, but not the key <backspace>. Should evil-mode perhaps trap <backspace> directly as well as DEL? Or is this a bug in haskell-mode, i.e. should haskell-mode be trapping DEL instead of <backspace>? -Keshav

2 2

A couple of questions
by Keshav Kini 13 Sep '13

13 Sep '13

Hello, First of all, thank you very much for your great work on evil! I'm really pleasantly surprised at how active your development is :) I'm a vim user who is trying to learn emacs without losing the handy modal editing of vim (as I imagine many others on this list are), and evil seems to be exactly what I need. I have a couple of questions. First, I am wondering if evil-want-C-u-scroll is broken. I have set it to t using M-x customize-group evil-mode, which causes (custom-set-variables '(evil-want-C-u-scroll t)) to appear in my ~/.emacs , but I don't see any difference in the behavior of evil. Is there something else I need to do in order to make C-u call evil-scroll-up (as C-h k C-d tells me that C-d is bound to evil-scroll-down)? Second, I am wondering about the behavior of :q . It seems to me that it behaves more like :qa does in vim. According to vim documentation, :q[uit] should "Quit the current window. Quit Vim if this is the last window.". So I guess it should be similar to kill-buffer in emacs, no? Thanks again! -Keshav

6 10

How to control Emacs vs. vi state with a file local variable?
by Christoph LANGE 04 Feb '13

04 Feb '13

Dear evil developers/users, I would like to generally open all files of a certain type (org-mode) in vi state but make exceptions for a few individual files. Using file local variables didn't work. I tried Local Variables: eval: (evil-emacs-state) End: but apparently the order of execution was the following: 1. load the file 2. apply the local variables, switching to Emacs state 3. here, or possibly before (2), switch buffer to org-mode 4. on seeing that org-mode is not in the list of evil-emacs-state-modes, switch to vi state If this assumption is right, is there any way of opening individual files in Emacs state? Cheers, and thanks in advance, Christoph -- Christoph Lange, http://www.facebook.com/ch.lange, Skype duke4701

3 2

Why does this not work the first time it's called?
by Guido Van Hoecke 28 Jan '13

28 Jan '13

I have a file that I want to visit, go to the second character of the fourth word, and enter replace mode: (defun guivho-test(name-of-file) "Visit file, goto fourth word, second char and enter replace mode" (interactive "fName of file: ") (find-file name-of-file) (beginning-of-line) (evil-forward-WORD-begin 3) (evil-forward-char) (evil-replace-state)) Test-file contents: line1 word1 word2 word3 line2 word1 word2 word3 line3 word1 word2 word3 line4 word1 word2 word3 I do not understand why the last the evil-forward-char and the evil-replace-state do not work when the file is not yet loaded, but do work if the guivho-test is executed from the buffer that already has the file. The first run leaves the cursor on the begin of the fourth word, ans it remains in normal mode; executing it again does advance the extra character and switches to replace mode. Can somebody explain this? TIA, Guido -- Under a government which imprisons any unjustly, the true place for a just man is also in prison. -- Henry David Thoreau http://vanhoecke.org ... and go2 places!

2 4

Comment region broken?
by Sanel Zukan 07 Jan '13

07 Jan '13

Hi, Anyone has problems with comment-region (C-c C-c) in c-mode? In stock emacs, if I go to line X and hit C-c C-c, without marking the region, emacs will report: 'The mark is not set now, so there is no region'. However, in evil mode, when I do the same, emacs will first hit a CPU on 100% and comment every line from the start of file up to that line. Undo of above operation will again put CPU on 100% and after a few secs. it will revert those comments. Should I report this as an issue? Regards, Sanel

2 1

evil-mode evil-lookup-func question
by Daniel Friedman 06 Jan '13

06 Jan '13

Hi everyone, I'm quite new to hacking elisp (and this mailing list), so please bear with me! For the past week, I've been customizing evil-mode to fit my needs. Recently, I've been having trouble setting the evil-lookup-func variable. I want to add mode-hooks so that when I hit "K" (upper-case) on a token in a buffer, the lookup functions that is called is appropriate to the file type. For example, I'm trying to add a hook to python-mode so that the evil-lookup-func variable is set locally to py-documentation, but it's not working. Here is my current mode-hook: (defun my-python-mode-hook() (setq evil-lookup-func #'py-documentation)) (add-hook 'python-mode-hook 'my-python-mode-hook) When I hit "K" on a token in a python-mode buffer, I get the following error: funcall: Wrong number of arguments: (lambda (w) "Launch PyDOC on the Word at Point" (interactive (list (let* ((word (thing-at-point (quote word))) (input (read-string (format "pydoc entry%s: " (if (not word) "" (format " (default %s)" word)))))) (if (string= input "") (if (not word) (error "No pydoc args given") word) input)))) (shell-command (concat py-shell-name " -c \"from pydoc import help;help('" w "')\"") "*PYDOCS*") (view-buffer-other-window "*PYDOCS*" t (quote kill-buffer-and-window))), 0 There are two main things that I need help with: 1. Why am I getting this error, even when there is a word under the point? How can I resolve this bug? 2. How do I make this hook only apply to python-mode buffers? When I hit "K" in any buffer, it calls this function. I'm sure there's a simple solution, but like I said, I'm very new to elisp. Thanks! D

2 1

Strange visual selection in scheme mode
by Sanel Zukan 05 Jan '13

05 Jan '13

Hi, I'm have odd behavior inside visual selection (actually when is going to be made comment block). In attachment is offending file. To reproduce it, open it, got to beginning, hit CTRL-V and start to go down (using down button). Now, the cursor will be stuck in line before '(define (coroutine-maker proc)...' I'm not sure what is happening with just that line, but if you skip it, selection will work without problems. I also noticed that selection line now became only partially visible; after reverting code to some older branch I keep for reference (b6fc1e2c8e5d488dabd3068417faf94b768115b9), that line behaves exactly as in vim: the first column will be always highlighted. Idea what could be wrong? I'm using emacs 24.1.1, daemonized in terminal. Regards, Sanel

2 4