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

Binding [tab] and C-i in viper-vi-basic-map
by Štěpán Němec 14 Jul '10

14 Jul '10

After having actually run the new code (current version of which was introduced in commit 4dfbed11308), I commented the two lines out ;; (define-key viper-vi-basic-map [tab] (or (key-binding [tab]) ;; (key-binding "\C-i"))) because for me it brought one problem -- the code binds <tab> at the point of loading Vimpulse to some binding <tab> happens to have at that time; but the binding also overrides any major mode maps, so e.g. in Org mode, I now got `yas-expand' on <tab> instead of the previous and correct `org-cycle' in Vi state (because Vi state originally had no binding for <tab> at all, it worked just fine). While I understand what the change was supposed to do, I don't really understand *why* you did it. Vegard? Does it solve any problems or bring any actual advantages? I don't feel too strongly about it, because in Vi state there is no universal way to have major mode bindings respected, i.e. it's just a fortunate coincidence that <tab> was unbound in Vi state; the only safe way is to use Emacs state for the mode or mess with the Viper maps. OTOH, I really don't see why you made that change, so I figured I'd ask. ;-) Štěpán

2 4

RE: For hideshow mode, don't hide all lines by default
by Štěpán Němec 14 Jul '10

14 Jul '10

commit dbf7305dbde4737d73748ae31e724e722ef0ce34 Author: Stephen Bach <git(a)sjbach.com> Date: Fri Jul 9 13:44:46 2010 -0400 For hideshow mode, don't hide all lines by default --- vimpulse-compatibility.el | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/vimpulse-compatibility.el b/vimpulse-compatibility.el index c2c59f0..9d0adae 100644 --- a/vimpulse-compatibility.el +++ b/vimpulse-compatibility.el @@ -294,7 +294,6 @@ (eval-after-load 'hideshow (hs-toggle-hiding) (hs-hide-level vimpulse-fold-level)) (defun vimpulse-hs-setup () - (hs-hide-all) (define-key viper-vi-basic-map "za" 'vimpulse-za) (define-key viper-vi-basic-map "zm" 'hs-hide-all) (define-key viper-vi-basic-map "zr" 'hs-show-all) Why? Isn't that what Vim does, when you turn folding on? (It would have been nice to have the rationale in the commit message, providing there is one). I don't use hs-minor-mode, but a possible reason for this change I can think of is that it breaks existing Emacs user expectations, because the mode hook triggers the hiding unconditionally. Is that it? Štěpán P.S.: Up to 99fb1aaa1e5, commit summaries end with a period. Then there are four commits without and one with a period again. Just felt like mentioning that. >_>

3 2

[Vimpulse] status of vimpulse-connect-undos
by Stephen Bach 11 Jul '10

11 Jul '10

I've spent the last couple days updating my ancient personal viper/Vimpulse configuration to the current devhead. Pretty happy, especially with these: - working visual mode - text objects - /- and ?-style searching integrated with isearch for better highlighting So, great work. :-) It's really nice to see development moving forward again. Now, the single impacting regression I've run up against so far is with undo. Unlike Vim and my old version of Vimpulse, reverting a change with e.g. "cw" requires two undos instead of one. This is a pretty significant deviation, at least for my workflow. I scanned through the code and saw vimpulse-connect-undos, currently disabled because of a dependency on undo-tree.el. A couple questions: 1. What makes undo-tree.el preferable to redo.el, for Vimpulse's purposes? 2. Is fixing "cw" and friends a priority, or is it something that users of Vimpulse have learned to live with? Thanks, Stephen

3 4

Assembla ticket creation requires administrative privileges?
by Štěpán Němec 05 Jul '10

05 Jul '10

Some evidence suggests that the Assembla bug reporting procedure recommended in multiple Vimpulsy places is actually only available to project members. I quote here the relevant part of today's discussion on the Vimpulse Emacs Wiki page (<http://www.emacswiki.org/emacs?action=browse;id=Vimpulse>): ===START-QUOTE=== I am logged in (as alexey_r), but can’t create a ticket there: > 403 Forbidden (TICKET_CREATE privileges are required to perform this operation) Anyway, the ticket I wanted to create is an enhancement request to add hlsearch. One possible solution can be found at http://r4yner.wordpress.com /2008/09/19/hlsearch-for-emacs/ [N.B. the above is by Alexey] Well, the interface seems to suck somehow (I didn’t investigate): when I tried to create a ticket, a login dialog popped up, and when I entered the same login information as with my Assembla account, I could create a ticket (i.e., you have to kinda log in twice). Does that not work for you either (I’m a project member, so maybe I have some extra privileges, no idea)? [...] [N.B. the above is by me] No, it doesn’t work. It seems you do have to be a member to create a ticket. – AlexeyRomanov ===END-QUOTE=== Vegard, do you have any idea? I guess I could read some of the documentation on the Assembla site and try to figure it out, but I'm a bit Traco- and unknown-wiki-system-and-Assembla-in-general- phobic and IIRC you seemed to like it, so I'm still hoping you could shed some light on the issue. Alexey, do I understand correctly that you did get the login dialog in the browser when trying to create a new ticket, but when you entered your Assembla login and password there, you got some error? Štěpán

3 6

[Vimpulse] Strnge behavior in Info (and probably other modes)
by Alessandro Piras 05 Jul '10

05 Jul '10

When I M-x info, I get the full viper bindings. However, after a random amount of time, or maybe after I do some other stuff (like running gnus on another frame it seems) the nice vimpulse bindings get loaded. I don't really get what's going on, and I don't really know what do I do to trigger the loading. This time it was gnus, but I think other times it has been something else, maybe org-agenda. Do you have any idea what's going on? __ Alessandro

2 5

hlsearch in Vimpulse
by Alexey Romanov 05 Jul '10

05 Jul '10

Hello! First, I really need to say that Vimpulse is great. Text objects were the first thing I've tried to use in Viper and was disappointed in their absence. Would it be possible to include Vimpulse as part of Viper at some later date? Second, as I've mentioned on the EmacsWiki page, hlsearch would be nice to have. One possible way to add it is described at http://r4yner.wordpress.com/2008/09/19/hlsearch-for-emacs/. Perhaps, even if it shouldn't be added as a part of Vimpulse, it could be added to the Tips&Tricks page? Yours, Alexey Romanov

3 3

[vimpulse] Bug: TAB doesn't autocomplete in minibuffer.
by Alessandro Piras 03 Jul '10

03 Jul '10

One of the recent changes in vimpulse broke the behavior of the tab key in the minibuffer. It now inserts a TAB character instead of triggering the usual autocomplete function. __ Alessandro Piras

3 16