- implementations-list - lists.ourproject.org

[implementations-list] Whether Vimpulse may intentionally work differently than Vim (was: [PATCH] Vimpulse: vi* and va* ...)
by Jason Spiro 01 Dec '09

01 Dec '09

2009/11/29 José A. Romero L. <escherdragon(a)gmail.com> wrote: > [...] > [...] I've divided the original patch into > 3 smaller ones: one for removing the extra definitions of the function > vimpulse-visual-replace-region, and two for the vi*/va* stuff, the first > one with standard gvim behavior, and the second one with a function of > my own invention that IMO makes that behavior more useful. > [...] I always tried to make sure Vimpulse worked as much like Vim as possible. If somebody thought Vim behavior could be improved, then I wanted them to email the Vim mailing list and get the change made in Vim. Once the change was made in Vim, then the same change could be made in Vimpulse. This would provide two advantages. * People who use both Vim and Vimpulse could use the same keys in both. * It would be possible to one day copy and paste from the Vim documentation into the Vimpulse documentation, maybe by an automated Vimpulse .txt-format-help-file-generation script. But now that Alessandro is maintainer, it is his choice whether to continue to enforce this policy or not.

2 1

[implementations-list] Re: Re: [PATCH] Vimpulse: vi* and va* object selection implementation proposal
by José A. Romero L. 30 Nov '09

30 Nov '09

Hi Jason, 2009/11/22 <implementations-list-request(a)lists.ourproject.org>: (...) > * Next time you write a patch, write [PATCH] in the subject line. I > have done this for you now. Sure will, thanks. > * There's no need to attach all of Vimpulse -- just the .patch file. > That is why your mail was automatically held until I approved it: > your mail exceeded I think 128K. I see. When considering a patch I usually like to examine both the patch itself and the modified code, to see how it "merges" with the rest. But sure, next time I will attach only the patch. > Now some questions: > > 1. Do you agree that when Vimpulse finally gets into Emacs, you will > be able to mail or fax in a copyright assignment saying that your work > will no longer be copyrighted by you but by the FSF? Can you please > private-mail to me and Alessandro your phone number and either your > home or work snail mail address? We don't plan to use it except for > asking you for copyright assignment if needed. I have no problem with that -- I'm already enjoying the advantages I wanted from writing that code, anyway. Just out of curiosity: do you have already any schedule or estimation of when the FSF will consider adding Vimpulse to the official Emacs distribution? > 2. On which Emacs and/or XEmacs versions did you test your patch? I'm currently using: GNU Emacs 23.1.50.2 (i686-pc-linux-gnu, GTK+ Version 2.16.1) of 2009-10-11 on spleen checked out from CVS a few weeks ago, but right after reading your message I thought of testing it on: GNU Emacs 22.3.1 (i486-pc-linux-gnu, GTK+ Version 2.16.2) of 2009-06-26 on rivendell, modified by Debian from the Debian package in Sid, and I realized that in Emacs 22 the function activate-mark does not exist, so we'll have to take care of that difference. Besides that one detail, my modifications seem to be working fine there too. > 3. Your patch got from GNU Mailman's admindb to my personal inbox, > but not to the mailing list when I approved it. So Alessandro must > retrieve the patch from his own inbox too. This is probably because > you exceeded some size limit. But anyway it looks like you patched > the released version of Vimpulse. Do you know how to use svn and > emerge? If so, could you please send a new version of your patch > which patches the multi-file svn version of Vimpulse? (Alessandro may > make more requests of you. For example, he may ask you to make the > vimpulse-visual-replace-region dup removal a separate patch; but I > think he probably won't ask that.) I do use SVN on a regular basis, at work as well as for keeping my own stuff, just let me know the repository URL (the only version of Vimpulse I know is the one I got from the Emacs Wiki) and I can patch that. I've never used Gentoo though, so I have no idea how to use emerge, nor how does it relate to SVN besides installing it in the local box (or were you talking about something different?) > Thanks again for the patch. My pleasure :) Cheers, -- José A. Romero L. escherdragon at gmail.com "The opposite of war is not peace, it's creation." (Jonathan Larson)

3 3

[implementations-list] {Spam?} Descargue ahora y amase su fortuna
by C A S I N O 28 Nov '09

28 Nov '09

¡Descargue ahora y amase su fortuna! http://www.gamegoldmummy.net/es/ -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0

[implementations-list] Disfrute de la oferta real en Casino Royal
by Royal Casino 27 Nov '09

27 Nov '09

Obtenga una oferta real en el Royal Club Casino! Con un bono de bienvenida de $400 usted puede comenzar a jugar con los últimos juegos de casino y grandes jackpots progresivos! Consiga hoy sus $400 y comience a jugar... http://www.royalplayland.net/sp/ -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0

[implementations-list] Vimpulse: vi* and va* object selection implementation proposal
by José A. Romero L. 22 Nov '09

22 Nov '09

Hello Vim fans, This is about the Vimpulse vim emulation for emacs. I've made some modifications to Vimpulse in order to add visual selection of text objects (vi* and va*) and a few other details, namely selection widening (e.g. try doing "va(" on some sexp and pressing "_" one or more times) and setting and activating the emacs mark when entering visual mode. Besides, I noticed that version 0.3.0 of Vimpulse contains three versions of the vimpulse-visual-replace- region function. I fixed that too. @Jason S, Alessandro P.: Would you have a look at it and let me know what you think? I'm sending in attachment the patch, as well as an already patched version of Vimpulse 0.3.0. Cheers, -- José A. Romero L. escherdragon(a)gmail.com "We who cut mere stones must always be envisioning cathedrals." (Quarry worker's creed)

2 1

[implementations-list] partially function application and prefix keys for Vi commands that take movement commands as arguments
by Bayle Shanks 13 Oct '09

13 Oct '09

I saw that in July, people were talking about alternative ways to program commands like "d" that take other commands (like "w") as arguments. Here's another proposal; make "d" a prefix key, and bind "d"->"w" to a partially applied "delete-cmd" function, with its first argument fixed to 'viper-forward-word. Use Elisp functions to create these bindings en masse, to remove the tedium of explicitly writing out bindings for each pair of movement command and movement-argument-taking command. Attached is elisp code that demonstrates this. The advantage is that you work within emacs's keymap system rather than replacing it. Apologies if this has already been discussed.

2 1

[implementations-list] hello; list archives; viper remap; 3 Qs
by Bayle Shanks 01 Oct '09

01 Oct '09

Hi, I just thought I'd mention that the mailing list archives end in July. Apologies if this has already been reported. While I'm here, I guess I should introduce myself and my project, and ask some questions. I've been using Emacs awhile but not at an advanced level. Recently I heard a rumor that Emacs is bad for one's hands due to chording, and I have RSI problems, so I thought I'd check out Viper. Since I'm learning something new anyway, I decided to remap the Viper keyboard layout with the goal of minimizing chording and maximizing efficiency. Here is my current layout idea: http://bayleshanks.com/tips-computer-viperRemap . I've already implemented most of it, but it's not done yet. Some of the Viper elisp functions hardcoded some of the keystrokes, so I modified those (work-in-progress is at http://bayleshanks.com/src/home/emacs.d/viper-cmds-remap.el)-- I'll submit this part as a patch to Kifer when it's done. In addition, in a separate file (http://bayleshanks.com/src/home/emacs.d/viper-remap.el) I added some options to optionally alter the functionality of some commands (e.g. the "substitute char" command can be made to return to Vi command Mode when you leave the substitution area) and am adding some new commands that conserve keyboard real estate (e.g. combine / and n, combine m and `). This file also contains the code to actually remap the keys to my remapped layout. I'll post again when I'm done. Both of these files are linked to from the page http://bayleshanks.com/tips-computer-viperRemap. Questions: there's a few things i'm considering changing but maybe there's a reason that i don't know for them being the way they are. Could anyone tell me what the motivation is for the following / in what common sequences of actions the following is more efficient than the alternative: * vimpulse's selection region being different from the Emacs region * the cursor moving back one when entering Vi command Mode (i know there's a config option if i want to change this, but why is it this way?) * p being "put after" whereas P is "put right here" (i would have thought P would be more commonly used) thanks, bayle

3 2

[implementations-list] C-v y p pastes "^BVimpulseVisualBlockMode^C" when experimental is nil (was: vimpulse - visual ...)
by Jason Spiro 30 Jul '09

30 Jul '09

On Thu, Jul 30, 2009 at 5:24 PM, Alessandro Piras <laynor(a)gmail.com> wrote: > yeah, that's an ugly hack I made to make p work with block selection. > before you had to press Ctrl-P to paste. Enabling the experimental > code should fix it. If Vimpulse pastes "^BVimpulseVisualBlockMode^C", isn't that a bug? :) P.S. Alessandro, it is best to get in the habit of always clicking "Reply to All" instead of replying to sender then forwarding to list. :) And John, it is best to join the list for long conversations like this: it makes it easier for us to reply, and then plus you can help out if you like by giving tech support to others in the future.

2 1

[implementations-list] Fwd: vimpulse - visual select with emacs -nw
by Alessandro Piras 30 Jul '09

30 Jul '09

---------- Forwarded message ---------- From: Alessandro Piras <laynor(a)gmail.com> Date: 2009/7/30 Subject: Re: vimpulse - visual select with emacs -nw To: John MacFarlane <jgm(a)berkeley.edu> yeah, that's an ugly hack I made to make p work with block selection. before you had to press Ctrl-P to paste. Enabling the experimental code should fix it. 2009/7/30 John MacFarlane <jgm(a)berkeley.edu>: > +++ Alessandro Piras [Jul 30 09 04:49 ]: >> better: >> (defadvice viper-intercept-ESC-key (around >> vimpulse-esc-exit-visual-mode activate) >> (when (and vimpulse-visual-mode >> (not (input-pending-p))) >> (vimpulse-visual-mode '-)) >> ad-do-it) > > I tried putting this in my .emacs, and it did allow the arrow > keys to be used with visual mode in console emacs. > > I noticed another glitch that doesn't seem connected with the > above code (since it happens even without it). If I do a > visual block select (Ctrl-v then movement keys), then y, > then P to paste the buffer, I get the string > > ^BVimpulseVisualBlockMode^C > > rather than the text I selected. > > John >

1 0

[implementations-list] vimpulse - visual select with emacs -nw
by John MacFarlane 30 Jul '09

30 Jul '09

I just discovered vimpulse and was very happy to find it! Thank you. One oddity: Visual selecting (with v or Ctrl-v) doesn't seem to work when I run emacs in a terminal with 'emacs -nw'. For example, in normal mode I can hit vllld and nothing will be deleted. Visual selecting works fine when I run emacs in its own window. Why would this be? Is there any way to get vimpulse working fully in terminal mode emacs? I don't subscribe to this list, so please cc me in replies. John

3 16