March 2012 - implementations-list - lists.ourproject.org

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

Is undo-tree dependency strictly necessary
by Leo Alekseyev 21 Jul '12

21 Jul '12

I was wondering if undo-tree is only there to match Vim behavior, and if I could use Evil without it. I actually find built-in Emacs undo functionality intuitive and I'm used to how it operates. On the other hand, I've run into some cases where undo-tree didn't behave as expected. If there are no ill consequences in using original Emacs undo vs undo-tree, it would be nice if it were configurable. --Leo P.S.: Thanks Frank and Vegard for quick bug-fixing action!

3 3

Protejase de Robos y Asaltos
by TELEVIGILANCIA 30 Mar '12

30 Mar '12

Clic aqui para desuscribirse de correos futuros: http://www.etools1.cl/box.php?nl=244&c=337&m=184&s=7135b867861dc5818a94983b…

1 0

Stuck in Emacs Mode when entering via Visual Mode
by Keshav Kini 23 Mar '12

23 Mar '12

Hi, I'm likely just doing something wrong, but I tried the following: 1) Visit a file - start in <N> mode 2) Type V to go to <V> mode 3) Type C-z to go to <E> mode 4) Type C-z to go to <V> mode again 5) Type ESC I would expect to be in <N> mode now, but Instead I end up back in <E> mode. What am I doing wrong? -Keshav

2 3

Which map is active when I overwrite text with R
by Titus von der Malsburg 22 Mar '12

22 Mar '12

In insert mode, I bind TAB to a custom expand function that is based on hippie-expand. However, when I overwrite text with the R command, I would also like to be able to use the expand function. During overwriting, TAB is bound to indent-for-tab-command and unfortunately it's not clear to me which map is active during overwrite. Could somebody please give me a hint? Thanks! Titus

2 4

[PATCH] Sort buffer names
by Sanel Zukan 14 Mar '12

14 Mar '12

Hi, Here is patch for sorted buffer names when ':ls" was given. I often use this command and when you have a bit of loaded files with various additional modes that opens own buffers, things becomes quite messy. This patch will apply sort on buffer names, so hidden buffers (those with " *xxx*") will be put first, then modes specific buffers (e.g. "*xxx*") and then goes files/directories. One nice feature would be numbering buffers, just like Vim does, so each buffer can be opened with ":b<n>". What do you guys think about it? Regards, Sanel

2 2

Keyboard Macros remain in input mode
by Zolrath 06 Mar '12

06 Mar '12

If I define a macro qw and perform some actions, when I use the macro via @w it plays back my actions appropriately but remains in input mode after playback. This differs from vim's macros which will return you to normal mode afterwards.

2 3

Why I stopped using viper, and am going to stop using Evil
by Matt Armstrong 02 Mar '12

02 Mar '12

I love the power of the vi/vim modal editing approach, and I applaud how far Evil (and all prior efforts, especially viper) take it in Emacs. I thought I'd write about why I'm not going to use Evil. I tried it for about a week. In the past, I've used viper for about a year before dropping it in favor of vim, which lasted another two years. Overall I have used Emacs for 18 years. In short: it is easier to use one editor at a time. By default, Evil presents you vim key bindings, but makes you use Emacs key bindings too: (a) see the huge list of modes in evil-emacs-state-modes (b) insert mode has Emacs key bindings On (a), most of these modes don't completely rebind the Emacs key map. In particular, they usually don't redefine how the point is moved, how buffers, windows and frames are managed, etc -- this is all vanilla Emacs stuff. In contrast, equivalent modes in vim use the vim key bindings and ex commands for doing all this stuff. On (b), Evil gives me M-q, C-a, C-v, etc. while in insert mode. This means I'm using two editors at once: vim and Emacs. In Evil, many very basic key bindings do wildly different things when switching from normal to insert mode and back: C-f, C-b, C-v, etc. Vim doesn't suffer from this (much) because insert mode is relatively free of key bindings. The vi -vs- Emacs dichotomy is always there, creating friction. This is certainly not the way Emacs would have designed its key commands were modal editing its initial design goal. I don't know what the solution is. In my ideal world, all Emacs key bindings would be entirely blown away and replaced with vim-ish ones. That's pretty audacious!

5 5