September 2010 - implementations-list

[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

the first session whereof began the 24 of Sep
by Decomo Kinnaman 29 Sep '10

29 Sep '10

E authoritie of a bishop, spake these words; "Bicause (saith he) thou wouldst not absteine from entring the house of that wicked person being accurssed, thou shalt die in the same house:" and so it came to passe. * * * * * _Suidhelme king of the Eastsaxons, he is baptised, the bishoplike exercises of Ced in his natiue countrie of Northumberland; Ediswald K. of Deira reuerenceth him, the kings deuout mind to further and inlarge religion;

1 0

[Vimpulse] `make big` target
by Stephen Bach 28 Sep '10

28 Sep '10

Hi, There seems to be a problem with the `big` Makefile target - the elisp produced appears to be unparseable, at least for me. ("End of file during parsing" -- and trying to track down paren imbalances is a dog, so I didn't try very hard to pinpoint the issue.)

3 4

[Vimpulse] substitute bug
by Daimrod 28 Sep '10

28 Sep '10

Hi, There is a problem with the substitute command in the case I want to substitute "something" by "set<space>something". So, the following command fails when I hit the space key. :s/something/set something The substitute command is simply cancelled. PS: I've the same problem than Stephen Bach with the `make big` command, but I didn't figure out how to reply to his mail because I've signed up for the list after his mail. However, I think the problem is in the file: "vimpulse-viper-function-redefinitions.el" line 907 (something is wrong with the brackets) PPS: Sorry if I made any mistake.

2 1

ut if we are free-
by Albert Sisneroz 23 Sep '10

23 Sep '10

Ney. Nearly the whole of the village was the property of a gentleman who had built the hotel and billiard-room, and run up a few lodging-houses on a speculation, which seemed at best a doubtful one, of making it in time a fashionable watering-place. Glyndewi had been recommended to us as a quiet place. It was quiet--horribly quiet. Not the quiet of green fields and deep woods, the charm of country life; but the quiet of a teetotal supper-party, or a college in vacation. "Just the place for reading: no gayety--no temptations." So I had written to tell the governor, in the ardour of my setting forth as one of a "reading-party:" alas! it was a fatal mistake. Had it been an ordinarily cheerful place, I think one or two of us could and should have read there; as it was, our whole wits were set to work to enliven its dulness. It took us as long to invent an amusement, as would have sufficed elsewhere for getting tired of half a dozen different dissipations. The very reason which made us fix upon it as a place to read in, proved in our case the source of unmitigated idleness. "No temptations" indeed! th

1 0

[ANN] Vimpulse 0.5
by Vegard Øye 12 Sep '10

12 Sep '10

http://www.emacswiki.org/emacs/vimpulse.el This release changes Vimpulse's dependencies: it now uses undo-tree.el instead of redo.el. undo-tree.el can be obtained from: http://www.emacswiki.org/emacs/UndoTree Just place it somewhere in your `load-path', and Vimpulse will load it automatically. (You can still use redo.el with XEmacs, but without the tree functionality of undo-tree.el.) News: - [NEW] :undolist or :ul shows the undo history as a tree. This uses undo-tree.el, which replaces redo.el for undo/redo. - [NEW] "/" and "?" use isearch. Matches are highlighted while typing; also, isearch shortcuts apply, like "M-c" to toggle case-sensitivity. Type "C-h k /" for more details. - [NEW] Keybinding functions: `vimpulse-global-set-key', `vimpulse-local-set-key', `vimpulse-define-key'. State bindings can be assigned to both minor and major Emacs modes, which is useful for extensions. - [NEW] Keys: "gi", "g0", "g$", "]P", "]p". - [NEW] Lower-case marks are buffer-local -- thanks, Štěpán Němec. - [NEW] If `viper-auto-indent' is t, then "RET" extends the comment prefix to the next line (with `comment-indent-new-line' from newcomment.el). - [NEW] "C-w" has its own prefix map, `vimpulse-window-map'. - [FIX] Replace mode's appearance is more similar to Vim's. - [FIX] Byte compilation errors. - [FIX] Various bugs submitted to the mailing list -- thanks, everyone. -- Vegard

1 0

[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

[OT] Git User's Survey 2010
by Štěpán Němec 09 Sep '10

09 Sep '10

Hello everybody, I just thought I bring this up in case anyone wants to contribute: Git has been organising a survey every year for some time, and now's the time to take it this year (up to October 15), so please do take the survey (it's not too long, can be fun and other than contributing a bit to development of our beloved VCS you might even learn about features mentioned there you had no idea about ;-)): http://git.wiki.kernel.org/index.php/GitSurvey2010

1 0

[Vimpulse] /-search incremental highlighting is always case insensitive
by Stephen Bach 02 Sep '10

02 Sep '10

Hi, I really like the new isearch-style /-search, but I notice the highlighting as I'm typing a search term, as well as the first search selection, are always case insensitive. So, given this text: ASDF asDf asdf If viper-case-fold-search is nil and I search for "asdf", all of the variants of asdf highlight, and after pressing enter the cursor moves to ASDF, but subsequent presses of "n" will only go to asdf (even though the other variants stay highlighted as if they are also matched). As a side-note, it'd be nice if the old viper trick of typing "/" twice quickly to change case sensitivity still worked -- but since this isn't a Vim thing, I can understand why we didn't bother keeping it around.

2 1

[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