Hi, I am hoping to use vimpulse in the following manner: To have it disabled globally, but bind viper-escape-to-vi to a custom key so I could perform a quick editing operation when necessary. I haven't found a documented way of doing this so far so I hope someone can help me with disabling viper globally... -- Regards, ~ argetek
On Mon, May 2, 2011 at 16:07, argetek senvx <[email protected]> wrote:
I am hoping to use vimpulse in the following manner:
To have it disabled globally, but bind viper-escape-to-vi to a custom key so I could perform a quick editing operation when necessary.
I haven't found a documented way of doing this so far so I hope someone can help me with disabling viper globally...
Doesn’t Ctrl-Z do this?
Hi! On Mon, May 2, 2011 at 4:03 PM, Nikolai Weibull <[email protected]> wrote:
Doesn't Ctrl-Z do this?
Yes, toggling it is fine but I am looking at the reverse direction in general: I want viper disabled (by default, globally) except for when I explicitly need it and, that too, should immediately switch back to normal emacs behaviour as soon as I perform that one-off operation. So, I want all buffers to start without viper and I haven't found a way to do that yet. I hope this description makes sense. -- Regards, ~ argetek
As we have discussed, 'viper-escape-to-vi' only switch to vi for one command, not sure if this is what you want. You can actually switch between vi state and emacs state by pressing 'C-z'. York On Mon, May 2, 2011 at 10:07 AM, argetek senvx <[email protected]> wrote: Hi, I am hoping to use vimpulse in the following manner: To have it disabled globally, but bind viper-escape-to-vi to a custom key so I could perform a quick editing operation when necessary. I haven't found a documented way of doing this so far so I hope someone can help me with disabling viper globally... -- Regards, ~ argetek _______________________________________________ implementations-list mailing list [email protected] https://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list
Sorry I didn't read the replies, but what's the point of switching to Vi for just one command? On Mon, May 2, 2011 at 2:39 PM, York Zhao <[email protected]> wrote: As we have discussed, 'viper-escape-to-vi' only switch to vi for one command, not sure if this is what you want. You can actually switch between vi state and emacs state by pressing 'C-z'. York On Mon, May 2, 2011 at 10:07 AM, argetek senvx <[email protected]> wrote: Hi, I am hoping to use vimpulse in the following manner: To have it disabled globally, but bind viper-escape-to-vi to a custom key so I could perform a quick editing operation when necessary. I haven't found a documented way of doing this so far so I hope someone can help me with disabling viper globally... -- Regards, ~ argetek _______________________________________________ implementations-list mailing list [email protected] https://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list
Hi, On Mon, May 2, 2011 at 7:47 PM, York Zhao <[email protected]> wrote:
Sorry I didn't read the replies, but what's the point of switching to Vi for just one command?
For one, it would allow an existing emacs user to test waters and transition into vimpulse without causing various regressions in their key bindings and workflows. :-) -- Regards, ~ argetek
On Mon, May 2, 2011 at 8:09 PM, argetek senvx <[email protected]> wrote:
Hi,
On Mon, May 2, 2011 at 7:47 PM, York Zhao <[email protected]> wrote:
Sorry I didn't read the replies, but what's the point of switching to Vi for just one command?
For one, it would allow an existing emacs user to test waters and transition into vimpulse without causing various regressions in their key bindings and workflows. :-)
I only want to be able to use terse editing commands occasionally eg for text objects. Because viper will be disabled the rest of the time, I can simply carry on using everything as I normally do with my fine-tuned configuration. -- Regards, ~ argetek
On Mon, May 2, 2011 at 8:21 PM, argetek senvx <[email protected]> wrote:
On Mon, May 2, 2011 at 8:09 PM, argetek senvx <[email protected]> wrote:
Hi,
On Mon, May 2, 2011 at 7:47 PM, York Zhao <[email protected]> wrote:
Sorry I didn't read the replies, but what's the point of switching to Vi for just one command?
For one, it would allow an existing emacs user to test waters and transition into vimpulse without causing various regressions in their key bindings and workflows. :-)
I only want to be able to use terse editing commands occasionally eg for text objects. Because viper will be disabled the rest of the time, I can simply carry on using everything as I normally do with my fine-tuned configuration.
The frequency will change and I might want to increase the Vi editing time occasionally (I used to be a Vim user a few years ago) but I don't want to invest time in viper's key binding settings and mode-specific overriding because I am waiting to invest that time when evil is available hopefully with its flexible design. -- Regards, ~ argetek
Add '(viper-toggle-key-action)' in .emacs to disable the vi mode, afterwards, whenever you want vi, hit "Ctrl-Z". But you still have to hit "Ctrl-Z" again to switch back to emacs state after the "one" vi command. Good luck On Mon, May 2, 2011 at 3:27 PM, argetek senvx <[email protected]> wrote: On Mon, May 2, 2011 at 8:21 PM, argetek senvx <[email protected]> wrote:
On Mon, May 2, 2011 at 8:09 PM, argetek senvx <[email protected]> wrote:
Hi,
On Mon, May 2, 2011 at 7:47 PM, York Zhao <[email protected]> wrote:
Sorry I didn't read the replies, but what's the point of switching to Vi for just one command?
For one, it would allow an existing emacs user to test waters and transition into vimpulse without causing various regressions in their key bindings and workflows. :-)
I only want to be able to use terse editing commands occasionally eg for text objects. Because viper will be disabled the rest of the time, I can simply carry on using everything as I normally do with my fine-tuned configuration.
The frequency will change and I might want to increase the Vi editing time occasionally (I used to be a Vim user a few years ago) but I don't want to invest time in viper's key binding settings and mode-specific overriding because I am waiting to invest that time when evil is available hopefully with its flexible design. -- Regards, ~ argetek _______________________________________________ implementations-list mailing list [email protected] https://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list
Hi York, On Mon, May 2, 2011 at 11:28 PM, York Zhao <[email protected]> wrote:
Add '(viper-toggle-key-action)' in .emacs to disable the vi mode, afterwards, whenever you want vi, hit "Ctrl-Z". But you still have to hit "Ctrl-Z" again to switch back to emacs state after the "one" vi command.
Thanks for your reply. I have tried but unfortunately to no avail. I still get viper mode enabled by default. Come to think of it, isn't the toggle operation buffer-local anyway? -- Regards, ~ argetek
Hi, On Mon, May 2, 2011 at 11:40 PM, argetek senvx <[email protected]> wrote:
Hi York,
On Mon, May 2, 2011 at 11:28 PM, York Zhao <[email protected]> wrote:
Add '(viper-toggle-key-action)'
Thanks to your suggestion I browsed the viper elisp code; I can see that (viper-change-state-to-emacs) is, at least, idempotent. If there is no easy way to globally disable viper after requiring vimpulse, then I could try to find an emacs hook (is there a buffer creation hook?) to add an invocation of this function to. I would also want to disable it for mini-buffer. -- Regards, ~ argetek
On Mon, May 2, 2011 at 11:51 PM, argetek senvx <[email protected]> wrote:
Hi,
On Mon, May 2, 2011 at 11:40 PM, argetek senvx <[email protected]> wrote:
Hi York,
On Mon, May 2, 2011 at 11:28 PM, York Zhao <[email protected]> wrote:
Add '(viper-toggle-key-action)'
Thanks to your suggestion I browsed the viper elisp code; I can see that (viper-change-state-to-emacs) is, at least, idempotent. If there is no easy way to globally disable viper after requiring vimpulse, then I could try to find an emacs hook (is there a buffer creation hook?) to add an invocation of this function to.
ISTM change-major-mode-hook is a more appropriate hook. -- Regards, ~ argetek
ISTM change-major-mode-hook is a more appropriate hook.
This hasn't worked out for me, I tried: (remove-hook 'change-major-mode-hook 'viper-major-mode-change-sentinel) (add-hook 'change-major-mode-hook (lambda () (viper-change-state-to-emacs)))
I would also want to disable it for mini-buffer.
http://gitorious.org/vimpulse/pages/Tips lists: (remove-hook 'minibuffer-setup-hook 'viper-minibuffer-setup-sentinel) (defadvice viper-set-minibuffer-overlay (around vimpulse activate) nil) (define-key minibuffer-local-map (kbd "ESC") 'abort-recursive-edit) This works well. -- Regards, ~ argetek
On 5/2/2011 8:18 PM, argetek senvx wrote:
http://gitorious.org/vimpulse/pages/Tips lists:
(remove-hook 'minibuffer-setup-hook 'viper-minibuffer-setup-sentinel) (defadvice viper-set-minibuffer-overlay (around vimpulse activate) nil) (define-key minibuffer-local-map (kbd "ESC") 'abort-recursive-edit)
This works well.
How about toggle-viper-mode ? it seems to turn off things globally
participants (4)
-
argetek senvx -
Isaac -
Nikolai Weibull -
York Zhao