- implementations-list - lists.ourproject.org

[implementations-list] Messing around with viper and its extensions
by Konrad Scorciapino 02 Jan '10

02 Jan '10

Hey guys, I'd been using vim for 5 or more years, until about a month ago, when I switched to Emacs to have access to better Lisp utilities. From day 1, I've been wanting to improve Viper, and my conversation some days ago with Jason at #emacs inspired me, so I played a bit with it and its extensions, and here I am to report the results. First I played a bit with vimpulse.el and viper-in-more-modes.el, fixing the extensions to the Emacs Mode. The visual mode evaluation wasn't working at all. First, the variable which was used to check if the user was on the visual mode was prefixed with viper-, but since I could only find it in vimpulse.el, I changed the prefix. Secondly, for some reason, the function '(vimpulse-set-mark)' was commented in vimpulse.el, so I had to uncomment it. I also changed a bit some other functions and got the Visual Line mode working more consistently. Besides that, I started to write viper bindings to ibuffer-mode. My idea is to write bindings for all modes a user might possibly find, thus providing a vi-like experience everywhere. I've attached the patches relative to the files I've changes. This is my first experience with elisp programming, so criticism of any kind is welcome. Thanks, and happy new year :-)

2 2

[implementations-list] fork viper?
by John J. Foerch 01 Jan '10

01 Jan '10

Hi, I don't use Viper myself so take this with a grain of salt.. Have you considered forking viper, instead of having all these modes that run on top of it? Having many modes that must work in concert with each other introduces a level of complexity that was a large part of why I decided not to use Viper anymore. -- John Foerch

2 1

[implementations-list] Fwd: Messing around with viper and its extensions
by Konrad Scorciapino 01 Jan '10

01 Jan '10

For some reason my message wasn't delivered, so I forward it here. A happy 2010 for everyone! ---------- Forwarded message ---------- From: Konrad Scorciapino <konrad(a)scorciapino.com> Date: Thu, Dec 31, 2009 at 6:23 PM Subject: Messing around with viper and its extensions To: implementations-list <implementations-list(a)lists.ourproject.com> Hey guys, I'd been using vim for 5 or more years, until about a month ago, when I switched to Emacs to have access to better Lisp utilities. From day 1, I've been wanting to improve Viper, and my conversation some days ago with Jason at #emacs inspired me, so I played a bit with it and its extensions, and here I am to report the results. First I played a bit with vimpulse.el and viper-in-more-modes.el, fixing the extensions to the Emacs Mode. The visual mode evaluation wasn't working at all. First, the variable which was used to check if the user was on the visual mode was prefixed with viper-, but since I could only find it in vimpulse.el, I changed the prefix. Secondly, for some reason, the function '(vimpulse-set-mark)' was commented in vimpulse.el, so I had to uncomment it. I also changed a bit some other functions and got the Visual Line mode working more consistently. Besides that, I started to write viper bindings to ibuffer-mode. My idea is to write bindings for all modes a user might possibly find, thus providing a vi-like experience everywhere. I've attached the patches relative to the files I've changes. This is my first experience with elisp programming, so criticism of any kind is welcome. Thanks, and happy new year :-) -- Et Forum delendum est!

1 0

[implementations-list] Thanks for having contributed to Viper / Vimpulse / viper-in-more-modes
by Jason Spiro 01 Jan '10

01 Jan '10

Dear (in alphabetical order) Alessandro, Brad, Michael, Vegard, and everyone else who contributed to viper / vimpulse / viper-in-more modes, Thank you. :) -Jason -- Jason Spiro: software/web developer, packager, trainer, IT consultant. I support Linux, UNIX, Windows, and more. Contact me to discuss your needs. +1 (416) 992-3445 / www.jspiro.com

2 1

[implementations-list] viper-in-more-modes for Haskell, Ruby, Prolog, and maybe AucTEX (was: Re: viper-in-more-modes)
by Jason Spiro 28 Dec '09

28 Dec '09

> From: Alexey Romanov <alexey.v.romanov(a)gmail.com> > Date: Thu, Jun 12, 2008 at 10:24 AM > > I've been using both Vimpulse and viper-in-more-modes and extended > vimm to Haskell, Ruby, Prolog and LaTeX (from AucTEX) modes. > I'm sending you the modified file. Ruby, Haskell, and Prolog work, but > LaTeX doesn't. > > For some reason > (viper-modify-major-mode 'LaTeX-mode 'vi-state my-LaTeX-modified-vi-map) > doesn't seem to work, since my-LaTeX-modified-vi-map has the correct value. [snip] cc: implementations-list By the way, if viper-in-more-modes one will be ready to include in upstream Emacs, will you then be willing to sign and submit a copyright assignment form to the FSF? Also, are you willing to privately mail me either your home or work mailing address and/or phone number, for use at that time? This is completely optional, but it'd be good if you're willing to do it. If you do it, I recommend you send it as a separate email, not CCed to implementations-list. Kind regards, -Jason

1 0

[implementations-list] Welcome, Vegard, our newest committer (was: Helping to maintain Vimpulse)
by Jason Spiro 28 Dec '09

28 Dec '09

On Wed, Dec 23, 2009 at 11:02 AM, Alessandro Piras <laynor(a)gmail.com> wrote: > it's ok for me. > Alessandro Piras Good. Vegard, thank you very much for offering to help. Vegard, the rest of this email is for you, but anyone else is free to read it also if they want. I added you as a Vimpulse "team member" on Assembla. Vimpulse's Assembla space (project page) is www.assembla.com/spaces/vimpulse. You should now be able to do anything you want in Trac and SVN. If I am wrong about this, please let me know. You can help us as much or as little as you want. After you do any patch reviewing or other work which gets included in Vimpulse, please add yourself to the Acknowledgements file. Since you're new, I think it'd be better if you not commit your own patch until at least one person other than you has tested it and told you it works for them on their version of *macs. This can be a friend or classmate of yours, or someone on IRC (Vimpulse has no IRC channel yet, but Emacs has one), or someone on the mailing list. Dear list: Would one of you please volunteer to test Vegard's patch and check that it works? You can do whatever else you like. Something useful, I think, would be to deal or help deal with open issues in Trac. But note that the lower issue numbers -- I don't remember which but maybe up to about #5 -- are old patches that I never got around to dealing with, and ended up forwarding the entire emails to Trac. They're probably bitrotted by now. They're probably more work to deal with. It might help to ask the original patch senders to fix them up so you can review and maybe commit. Ask them to resend as a patch to current SVN. When it's time to release a new version, type "make" to run the cat command listed in the Makefile, then copy and paste the entire contents of vimpulse-big.el into EmacsWiki. We release often. Release whenever you want. The steps to do include editing the version and Changelog top version, and testing to make sure that Vimpulse will load and work on your version of Emacs and XEmacs. Create an svn tag too. I think it would be best if every EmacsWiki version corresponded to some SVN numbered revision. After you release, bump the version in svn by adding "+svn" to its number. When you merge in any patch, you should edit Changelog and probably Acknowledgements. Always make a comment in SVN when you commit. Make svn commits often. If you want, just copy and paste your Changelog comment into the svn commit comments field. I use M-q in Emacs to re-wrap comments in the area at the top of the file. For changes adding or significantly removing a copyright-significant amount of code, you should also add a copyright line with the author's name to Copyright, and ask the author to agree that they will sign a FSF copyright assignment form if and when Vimpulse gets into Emacs. I don't remember anymore what "copyright-significant" means. Maybe the huge copyright-related mailing list thread from earlier this year contains an answer? I don't remember. Vimpulse has horrible documentation. Our documentation policy so far has unfortunately often been lax. I'm about to write a mail to the list about this problem. You may have lots of questions. Ask us whatever you want, and ask questions as often as you want. There's no such thing as a stupid question. :)

2 5

[implementations-list] Fwd: viper-in-more-modes
by Jason Spiro 26 Dec '09

26 Dec '09

---------- Forwarded message ---------- From: Alexey Romanov <alexey.v.romanov(a)gmail.com> Date: Thu, Jun 12, 2008 at 10:24 AM Subject: viper-in-more-modes To: jasonspiro3(a)gmail.com Hello! I've been using both Vimpulse and viper-in-more-modes and extended vimm to Haskell, Ruby, Prolog and LaTeX (from AucTEX) modes. I'm sending you the modified file. Ruby, Haskell, and Prolog work, but LaTeX doesn't. For some reason (viper-modify-major-mode 'LaTeX-mode 'vi-state my-LaTeX-modified-vi-map) doesn't seem to work, since my-LaTeX-modified-vi-map has the correct value. About Vimpulse: if I have selected a region while in Normal mode, can I switch to Visual while keeping the selection? 'v' loses it. -- Yours, Alexey Romanov

2 2

[implementations-list] Helping to maintain Vimpulse (was: Transferring maintainership of Vimpulse)
by Jason Spiro 23 Dec '09

23 Dec '09

On Mon, Jan 26, 2009 at 12:21 AM, Stephen Bach <sjbach(a)sjbach.com> wrote: > > On Sun, Jan 25, 2009 at 01:52:03PM -0500, Jason Spiro wrote: >> >> Are you interested in taking over maintainership of Vimpulse? >> > I appreciate being asked, but I'm probably not the best choice to be the > formal maintainer. I'd certainly like to see further improvements to > vimpulse and a viper-in-more-modes, though. I use them every day. :-) Stephen, are you willing not to be a formal maintainer, but simply to download, test, and commit patches from Trac when Alessandro is busy? This would require that Alessandro bless you to be allowed to do so, but I am sure that Alessandro would.

3 5

[implementations-list] vimpulse-modal.el --- modal key bindings
by Vegard Øye 08 Dec '09

08 Dec '09

The :map, :imap and :vmap commands of Vim let one make two key mappings starting with the same sequence of characters without one overwriting the other. For example: :imap aa foo :imap aaa bar When Vim has read "aa" in Insert mode, it will wait for another character to decide whether to insert "foo" or "bar". If the user types "a", "bar" is inserted; if another letter, "foo" plus that letter. Compare with the analogous use of Emacs' `global-set-key' function: (global-set-key "aa" 'foo) (global-set-key "aaa" 'bar) Here, the first binding is simply overwritten by the more specific second. The end result is that "aaa" is bound to `bar', while any other sequence starting with "aa" is not bound to anything. The attached code provides a set of Vim-like or "modal" functions for making new keybindings "on top of" previous bindings. They are `vimpulse-map', `vimpulse-imap' and `vimpulse-vmap', which mimic Vim's commands, and `vimpulse-define-key', a generic function for specifying the keymap. To load it, issue (require 'vimpulse-modal) Then, for example, the key sequences "cae" and "dae" may be bound in vi (command) mode using `vimpulse-map': (vimpulse-map "cae" 'vimpulse-change-a-sexp) (vimpulse-map "dae" 'vimpulse-delete-a-sexp) This will execute `vimpulse-change-a-sexp' when typing "cae" in vi mode, while retaining keys like "cw" for "change word" or "cas" for "change a sentence". Just for demonstration purposes, `vimpulse-change-a-sexp' and `vimpulse-delete-a-sexp' are indeed real text object commands, defined and bound as shown at the end of the file. They act on Lisp S-expressions. I am not suggesting they be made part of vimpulse.el, just making a point about extensibility. Try it! And please comment. :) Vegard Øye _________________________________________________________________ Windows Live™ Mail. Flere kontoer på ett sted. http://download.live.com/wlmail

2 4

[implementations-list] [PATCH] Small fixes
by Vegard Øye 01 Dec '09

01 Dec '09

I have made a few fixes, attached to this e-mail as a patch (patch.txt). They are: * AUTOMATIC LOADING OF CL.EL: if cl.el isn't loaded already (Common Lisp extensions for Emacs), one gets error messages bemoaning undefined functions like `destructuring-bind'. Added (require 'cl) to fix this. * FIXED `TRAILING-NEWLINES' PARAMETER: corrected a small typo in the function `vimpulse-get-bounds-with-whitespace'. See http://www.emacswiki.org/emacs/vimpulse for details. I also took the liberty to remove any trailing whitespace (M-x delete-trailing-whitespace), which made the patch a bit larger than it otherwise would have been. The patch was made with the GnuWin32 version of diff, running on Windows XP, with the command diff vimpulse-old.el vimpulse.el> patch.txt where vimpulse-old.el is version 0.3.0 of Vimpulse, downloaded from http://www.emacswiki.org/emacs/vimpulse.el. Tested on GNU Emacs 23.1. Vegard Øye _________________________________________________________________ Nye Windows 7: PCen som passer for deg. Finn ut mer. http://windows.microsoft.com/shop

2 4