atom-vim-mode-plus
atom-vim-mode-plus copied to clipboard
Support macro (record by `q`, replay by `@`).
vim has the ability to record macros with q
I know and I can implement it, but I don't want to for now. Until I feel I can manage complex situation brought by Macro feature, I will postpone to provide macro.
You should see the following: https://github.com/JunSuzukiJapan/atom-keyboard-macros https://github.com/JunSuzukiJapan/atom-keyboard-macros-vim https://github.com/JunSuzukiJapan/atom-keyboard-macros-vim/issues/5
I have just started using Atom, about two days ago, having used vim for years.
Was just pointing those interested in the issue to an existing implementation, which doesn’t actually work very well with vim-mode… but it might be a start?
If you don’t get to it in time then in about 2 months I will do it myself (actually very interested in Electron).
OK, I think I won't implement macro feature within 2months or more. It's interesting if you can create it. For vim-mod-plus, I've released several packages as vim-mode-plus's plugin.
Wiki section have short instruction and list of vmp plugin packages for reference.
+1
PSA: this worked for me - got me macros in vim-mode-plus!
https://github.com/JunSuzukiJapan/atom-keyboard-macros-vim/issues/5#issuecomment-212849566 via @expelledboy
All you need to do is install atom-keyboard-macros-vim now. The author merged in vim-mode-plus support
https://github.com/JunSuzukiJapan/atom-keyboard-macros-vim/commit/4804fb4a67a7f325814d83f470225260912c1364
btw: atom-keyboard-macros doesn't fully support vim-mode-plus. Seems like a bunch of motions/commands are not supported. For example, df<something> will not be recorded in a macro.
I agree that atom-keyboard-macros does not provide extensive functionality, and it would be nice—if t9 gets a change—to provide macro replay/recording.
Somebody made a package a month ago for that (vim-mode-plus-macros).
PSA: all the current plugins mentioned in this thread are terribly broken to the degree I wouldn't bother with them. Any chance of revisiting this, @t9md?