July 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

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

[Vimpulse] Bug with cw on whitespace
by Stephen Bach 04 Aug '10

04 Aug '10

Hi, The "cw" key sequence doesn't seem to consume extra whitespace anymore. For example: _ text If the cursor is "_", and you type dw, all whitespace up to "text" is removed. If you type cw, only a single space is removed. Not too much of a nuisance, but something that would be nice to have working. Thanks :-)

2 2

Re: vimpulse C-o not using global marks ?!?
by Štěpán Němec 03 Aug '10

03 Aug '10

TheLonelyStar <nabble2(a)lonely-star.org> writes: > Hi, > > I use vimpulse. When I do C-o it jumps to the last mark in the current file. > Can i somehow make it use global marks? Hi, let's have this discussion on the vim-emulation list, which I am hereby Cc:-ing (and please remove the help list from the Cc: header when replying; I don't think most people here are interested in this). I consider this to be a problem, too, and even started to implement it before some time, but as I almost never use it and nobody else seemed to ever mention this, it remained a stub, i.e. it sort-of works, but a bit funnily and not quite as in Vim (yet). Here is what I came up with (you can apply the diff provided you use the Git repository, not the single vimpulse.el file): Štěpán

2 7

Re: Add vimpulse-want-quit-like-Vim customization variable.
by Štěpán Němec 03 Aug '10

03 Aug '10

Vegard, I don't understand purpose or motivation of this change (commit af7bc2369c72a9), could you please comment (and could you (and others whom it may concern) *please* add such comments to the commit messages as well)? Apart from the fact that I don't get why you made the change in the first place, I see other issues as well: Viper already includes a :quit command, which is about as faithful to the Vim behaviour as the trivial version used by Vimpulse.[1] Now you add a variable whose name suggests that it will be "like Vim", but it actually triggers the Vimpulse behaviour... [I don't care other than that it's weird (I don't use any Ex commands at all).] Thanks, Štěpán [1] Actually, each of the commands, i.e. `ex-quit' on one hand and the Vimpulse version on the other, pick a different part of what Vim's :quit command does.

2 3

surround.vim vimpulse extension
by Tim Harper 30 Jul '10

30 Jul '10

Did anybody else use surround.vim? I've missed it ever since I switched to Emacs. Finally, last night, I got up the energy to hack something together: http://gist.github.com/487846 Things that work: * Changes surrounding enclosures * add surrounding enclosures * delete sounding enclosures Not working yet: * Surround region with a tag * non-visual surrounding of regions (IE: ysiw") * repeat surround modifications I'm not extremely happy with my approach on how I'm looking into the delete/change commands. Basically, I'm hijacking them in doing an advise (as in defadvice) approach. Feedback welcome, but mostly, I hope this is enjoyed by somebody else. Tim

4 10

[Vimpulse] Bug with yE
by Stephen Bach 30 Jul '10

30 Jul '10

Hi, In the line below, try doing yE with the cursor on the + sign and then pasting somewhere: +foo bar Vimpulse should only grab +foo, but it grabs bar as well. If you remove the +, it grabs only foo as expected.

3 6

What private changes to Viper and/or Vimpulse do you have in your .emacs file?
by Jason Spiro 25 Jul '10

25 Jul '10

Hi all, I am curious: what private changes to Viper and/or Vimpulse do you have in your .emacs file? You can tell us: 1. an English-language summary of what your code does, or 2. the code itself, or 3. both. Cheers, -Jason

5 7

[PATCH/RFC] Add some tips for contributors.
by Štěpán Němec 25 Jul '10

25 Jul '10

--- [Side note: Committing people's patches edited is a no no. At least I strongly prefer having a discussion and resending the patch, possibly several times, to having my patch edited (and possibly borken, which seems to have happened with 9b9c0298530) and committed under my name. Or being asked "I'll commit this instead/squash these changes in, OK?".] .gitattributes | 1 + CONTRIBUTE | 32 ++++++++++++++++++++++++++++++++ Header | 3 ++- 3 files changed, 35 insertions(+), 1 deletions(-) create mode 100644 .gitattributes create mode 100644 CONTRIBUTE diff --git a/.gitattributes b/.gitattributes new file mode 100644 index 0000000..b362cfa --- /dev/null +++ b/.gitattributes @@ -0,0 +1 @@ +*.el diff=lisp diff --git a/CONTRIBUTE b/CONTRIBUTE new file mode 100644 index 0000000..70988e4 --- /dev/null +++ b/CONTRIBUTE @@ -0,0 +1,32 @@ +So you want to contribute? That's great, thank you! Here are some tips that +will help you make us cry with delight at the very sight of your patch: + +Patch format +------------ +- it's best if the patches are directly processable by Git (such as when using + `git-format-patch', `git-send-email' or the ---8<--- scissors trick) +- a nice way to have Git produce better diff hunk headers when working with + Lisp code is to add this to your config: + +[diff "lisp"] + xfuncname = "^\\(.*$" + +With this and an appropriate diff attribute definition (provided by the +.gitattributes file in the repository), it will be immediately visible which +top level Lisp form a particular hunk pertains to. + +Commit messages +--------------- +- the first line is a commit summary, usually a single sentence in imperative + (starting with a capital letter and ending with a period) short enough to fit + in a mail subject line +- after that and a blank line comes the commit message with a free form + explanation (optional for trivial patches) + +General coding guidelines +------------------------- +- keep it inside 80 columns when possible +- avoid trailing whitespace (Git can help you with that) +- if you're making bigger changes, it's a good idea to try byte-compiling + Vimpulse even though you normally don't (the compiler sometimes catches + issues not obvious when running uncompiled) diff --git a/Header b/Header index 99661ce..1b07281 100644 --- a/Header +++ b/Header @@ -41,5 +41,6 @@ ;; ;; Vimpulse is under active development. It works quite well with ;; GNU Emacs 22.3 and 23.2, as well as XEmacs 21.4.22. Patches and -;; feature requests are welcome. +;; feature requests are welcome (see also the file CONTRIBUTE in the +;; repository). -- 1.7.1

3 10

[PATCH] fixes issue where dT<char>/dF<char> would delete more than expected
by Tim Harper 25 Jul '10

25 Jul '10

given: (this-is-some-text|) dTe would result in: (this-is-some-t| dFe would result in given: (this-is-some-| This change resolves the issue by setting these operators to be exclusive, rather than incluse. --- vimpulse-operator.el | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/vimpulse-operator.el b/vimpulse-operator.el index fd9acda..8c985bb 100644 --- a/vimpulse-operator.el +++ b/vimpulse-operator.el @@ -742,12 +742,12 @@ type TYPE. A custom function body may be specified via BODY." ;; These motions need wrapper functions to repeat correctly. (vimpulse-operator-map-define viper-end-of-Word 'inclusive) (vimpulse-operator-map-define viper-end-of-word 'inclusive) -(vimpulse-operator-map-define viper-find-char-backward 'inclusive) +(vimpulse-operator-map-define viper-find-char-backward 'exclusive) (vimpulse-operator-map-define viper-find-char-forward 'inclusive) (vimpulse-operator-map-define viper-forward-Word 'exclusive) (vimpulse-operator-map-define viper-forward-char 'inclusive) (vimpulse-operator-map-define viper-forward-word 'exclusive) -(vimpulse-operator-map-define viper-goto-char-backward 'inclusive) +(vimpulse-operator-map-define viper-goto-char-backward 'exclusive) (vimpulse-operator-map-define viper-goto-char-forward 'inclusive) (vimpulse-operator-map-define viper-search-backward 'exclusive) (vimpulse-operator-map-define viper-search-forward 'exclusive) -- 1.7.1.1

2 2