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

[implementations-list] [ANN] Vimpulse has migrated to Git
by Vegard Øye 14 Apr '10

14 Apr '10

The Subversion repository is no more; we now use Git as our version control system. To clone Vimpulse's repository: git clone git://git.assembla.com/vimpulse.git This will give you a local copy of the repository with complete revision history. One immediate difference from SVN is that there is no "trunk"/"tags" folder structure. To revert to an earlier version: git checkout vimpulse-0.3.1 (Type "git tag" for a list of versions.) Back to the latest changeset: git checkout master Our bug tracker's URL has changed. It is now located at http://trac-git.assembla.com/vimpulse/report Vimpulse's Assembla space URL, however, is the same: http://www.assembla.com/spaces/vimpulse Jason Spiro and Alessandro Piras: I have reinvited you to the space. Please accept so I can restore your administrative rights. Vegard _________________________________________________________________ Windows 7: Se direkte-TV fra den bærbare PCen. Finn ut mer. http://windows.microsoft.com/windows-7

1 1

[implementations-list] buggy behaviour with Transient Mark Mode disabled
by Štěpán Němec 14 Apr '10

14 Apr '10

Hello Vegard, OK, I see you fix bugs sooner than I decide whether I should whine about it or look in the source... :-P (speaking about gu/gU moving to bol unconditionally). Not this one though: Vimpulse exhibits strange behaviour with Transient Mark Mode disabled, and I seem to recall that wasn't the case before that last update (to rev 199, but I don't really remember from which revision) of mine. One typical manifestation, even without involving selection at all: With TMM off, first `dd' in a buffer deletes the whole portion of the buffer up to that line. After this failure, it works correctly again ...until you set the mark, obviously. In short, the command seems to act upon the region instead of line when TMM is disabled. Similarly with `yy'. Best regards, Štěpán P.S.: Is there any chance of convincing you to just use one big file? I'd really appreciate that, especially after switching to a usable VCS. Last time I proposed that you said multiple files were advantageous for debugging -- what did you mean? I can't think of any such advantage myself. Heck, you made it to 6k, but there's still allout.el with 7151! ;-)

3 6

[implementations-list] h/j/k/l keys in Info mode (was: How important is a Vimpulse user manual? ...)
by Jason Spiro 10 Apr '10

10 Apr '10

On Wed, Feb 10, 2010 at 3:18 PM, Vegard Øye <vegard_oye(a)hotmail.com> wrote: >> From: jasonspiro3(a)gmail.com >> Date: Wed, 10 Feb 2010 03:52:13 -0500 [snip] >> I think people can just use the arrow keys and Enter in Info mode. :) > > Yes. But to the seasoned Vim user with his hands at the home row, the > annoyance will be there. (If you're going to use Vim keys in Emacs, > you're probably somewhat seasoned. :) Fair. > Anyway, I added some utility code to vimpulse-misc-keybindings.el in > changeset [58] to address this in time. The idea is that there are two > forms of vi navigation: the "core" commands, like h/j/k/l, and the > rest. The core commands should, in general, be available in every > mode, even if this means overwriting the mode's own bindings for these > keys. On the other hand, the rest of the vi navigation commands -- w, > e, b, f, etc. -- are optional: they are only added if their keys don't > already do something else. Thus w may move forward by words or it may > not, while h always moves one character to the left, no matter what. [snip] Interesting. I see, looking at the changeset[*], that this doesn't yet affect Info mode unless you uncomment the several lines of commented-out code starting with eval-after-load 'info in vimpulse-misc-keybindings.el. If you uncomment those lines, then in Info mode, what can you press to go back to the last Info node you read before? Surely "l", the "Last node" key, won't work. Cheers, -Jason ^ [*]. http://my-trac.assembla.com/vimpulse/changeset/58

3 11

[implementations-list] A bug in text object?
by INA Lintaro 01 Apr '10

01 Apr '10

Hello, I found a bug in text object. Using '* i w' at the beginning of a word preceded by a non-whitespace character does not work correctly. For example, 'd i w' at the position of 'b' in the text "foo (bar)" deletes '(', where I think it should delete 'bar'. -- Lintaro INA

2 1