August 2010 - implementations-list - lists.ourproject.org

[implementations-list] issue with viper-escape-to-emacs
by Fabian Braennstroem 25 Apr '11

25 Apr '11

Hello, with the new vimpulse, I have a problem escaping back to emacs mode. I need this option to run some traditional 'M-x' functions. Up to now I used: (define-key viper-vi-global-user-map (kbd "\\\\") 'viper-escape-to-emacs) Unfortunately, this does not work anymore, as using M(Esc) for the next command cancels this escape and inserts the second of the backslash into the buffer... Would be nice, if you have a hint! Regards! Fabian

3 11

[Vimpulse] Arrow keys don't work as motions
by Nick Smallbone 10 Sep '10

10 Sep '10

Hi, Typing a special key such as <right> in Operating-Pending mode currently causes Vimpulse to crash in vimpulse-range. I've included a patch that fixes this, so that (for example) y right yanks the character under point, as it does in Vim. However, after fixing this bug there is another problem. Namely, if I type y 2 right (to yank two characters), the keypress parser continues waiting for input so that the echo line reads y 2 right- and it keeps on accepting more input no matter how many times I press right, until I press a non-special-key motion such as $, when it finally runs the command. I couldn't work out what was going on here, so I gave up. The patch for the first bug is below, though. Oh, and thanks for Vimpulse! It's brilliant! Nick diff --git a/vimpulse-operator.el b/vimpulse-operator.el index 4b1f594..b4ff648 100644 --- a/vimpulse-operator.el +++ b/vimpulse-operator.el @@ -220,8 +220,9 @@ (defun vimpulse-range (message oldmsg) ;; With doubled operator ("gqgq" or "gqq"), set motion to current line. (if (or (eq vimpulse-this-motion vimpulse-this-operator) - (member (vimpulse-strip-prefix (this-command-keys) t) - '("g??" "gUU" "gqq" "guu" "gww" "g~~"))) + (member (vimpulse-strip-prefix (this-command-keys)) + (mapcar 'string-to-vector + '("g??" "gUU" "gqq" "guu" "gww" "g~~")))) (setq vimpulse-this-motion 'vimpulse-line) (setq vimpulse-this-motion (vimpulse-operator-remapping vimpulse-this-motion))))

3 7

[ANN] Vimpulse has moved to Gitorious
by Vegard Øye 01 Sep '10

01 Sep '10

Vimpulse has changed its hosting provider from Assembla to Gitorious. The project is now located at: http://gitorious.org/vimpulse The new Git repository can be cloned with: git clone git://gitorious.org/vimpulse/vimpulse.git I recommend just deleting the old repository and cloning the new, because I have modified the Git history to sort out some early SVN conversion mess. (If you have made local changes to the old repository, you can rebase them with `git rebase' or patch your work with `git format-patch' and `git am'. Sorry for the inconvenience.) -- Vegard

2 4

V% and c-x c-e
by Marc Weber 30 Aug '10

30 Aug '10

Hi list, Is it intentional that when selecting (message "arg") using V% (on a parenthesis) that this only works top-down, but not bottom up? Bottom up leads to parse error or such. Marc Weber

2 1

el-get and vimpulse
by Marc Weber 30 Aug '10

30 Aug '10

We all know the (lovely?) feature of Vim to treat no files ever as binary by default. Now el-get is using url-retrieve to fetch tar files and using write-file to write it. Now either vimpulse (or Viper?) is appending a trailing \n which makes tar complain about trailing garbage exiting with code 2. How would you recommend to solve this issue? I didn't start reading much vimpulse / Viper code yet. Maybe there is a simple option (?) Marc Weber

2 1

ex: No file on this line
by George V. Reilly 24 Aug '10

24 Aug '10

I've managed to do this several times, but I don't know yet how to repeat it. I know about `C-h l', but I haven't spotted the pattern. After making various mistakes that I've canceled with C-g and/or C-], I get Ex into a state where I can't type SPC after `:e'. As soon as I hit SPC, instead of offering the directory path of the last file, I get a "No file on this line" error. The only way that I've found so far of fixing it is to quit Emacs and start a fresh process, which is no fix at all. -- /George V. Reilly george(a)reilly.org Twitter: @georgevreilly http://www.georgevreilly.com/blog http://blogs.cozi.com/tech

1 0

vimpulse bug: visual-line does not select final newline
by Craig Tenney 24 Aug '10

24 Aug '10

Hello, Using a recent snapshot of vimpulse (0.4+git, downloaded 08/2010) in Emacs 23.2.1, it appears that linewise-visual mode (V) often fails to select the trailing newline in the last line. This causes unexpected results (i.e. not like vim) when used with the delete (d) and yank (y) commands (and probably others). Similar behavior can be observed using characterwise-visual mode (v) (e.g. '0v$' also fails to select the trailing newline). For example, starting with: one two three and the cursor on line 'two', pressing 'Vd' results in: one three rather than the expected: one three Similarly, pressing 'Vyp' results in: one ttwowo three rather than: one two two three Similar oddities result for variations with multiple lines, using characterwise-visual mode, et cetera. I'm assuming this is tied up in the visual-expand/contract-functions and associated needs-newline variables. Thank you to the developers and contributors to vimpulse. Finding it has allowed me to consider using Emacs. Regards, Craig

4 14

Equivalent of 'hidden'
by George V. Reilly 23 Aug '10

23 Aug '10

I used VIP then Viper regularly in the late '80s and throughout most of the '90s, until Vim got good enough to be my primary editor. I haven't used Viper since Emacs 19 and I'm trying Vimpulse for the first time. Is there an equivalent to Vim's 'hidden' option? Every time I use C-^ to switch to the alternate buffer, I'm getting an annoying message about "Buffer foo is modified. Discard changes? (yes or no)". If I switch with :b or "C-x b", I don't get that message. Vimpulse (or Viper?) doesn't seem to work terribly well with Aquamacs 2.1. They work a lot better with Emacs 23.2 from http://emacsformacosx.com/. The most obvious thing being that I have to explicitly do M-x viper-mode, despite having (require 'vimpulse) in my ~/.emacs.d/init.el. Thanks. -- /George V. Reilly george(a)reilly.org Twitter: @georgevreilly http://www.georgevreilly.com/blog http://blogs.cozi.com/tech

2 2

[Vimpulse] "Not enough arguments to format string"
by Stephen Bach 20 Aug '10

20 Aug '10

Hi, There's some code in vimpulse-range and a couple other functions to save and restore the message stored in the echo area. It's got a small bug because of this behaviour of (current-message): (message "%%s message) --> displays "%s message string" (progn (message "%%s message string") (current-message)) --> returns "%s message string" (progn (message "%%s message string") (message (current-message))) --> (error "Not enough arguments for format string") Seems like the string returned by current-message should be escaped for % before redisplay.

3 4

Viper ESC in terminal Emacs
by Stephen Bach 08 Aug '10

08 Aug '10

Hi, Has anyone on this list managed to get a zero-delay viper ESC working in terminal Emacs? Works fine for me in a windowing system; ESC promptly switches from insert mode to normal mode. But from a terminal there is a highly annoying ~1 second delay after pressing ESC. In GNU Emacs 22 I believe I was able to solve this with: (setq-default viper-ESC-keyseq-timeout 0) This doesn't hold for Emacs 23. Notably, viper-ESC-keyseq-timeout has changed from a variable to a function in more recent versions of Viper. But even the following doesn't help: (defadvice viper-ESC-keyseq-timeout (around fix-viper-terminal-ESC activate) (setq ad-return-value 0)) My investigation seems to show that the delay happens before the toplevel viper-intercept-ESC-key is even called... ESC is a prefix key in non-Viper Emacs, so that could be the culprit, but ostensibly its status as a prefix key is shadowed by enabling Viper. Any ideas? Thanks, Stephen

2 4