-
Notifications
You must be signed in to change notification settings - Fork 2.5k
macros! #2230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
There was a similar request #910 But in general I would definitly vote for thi feature and give a usecase: |
Unfortunately, this is quite hard to implement. Because many things in Vimium happen asynchronously, we don't really know when one command ends, so we don't know when to launch the next one. Also, injecting keyevents into all of the different parts of the code base touched in your example, @a-b, would be a nightmare. |
Still, macros are really helpful and speed things up. Even a buggy implementation would be nice to have. Especially considering that current extensions for ff are going to die a "natural" death (thanks mozilla) and vimium seems to be the only ray of hope (#2425) on the horizon. Current ff extensions also have some bugs when it comes to macro support (e.g. vimperator/vimperator-labs#588), but it's a lot better than having nothing at all. |
@smblott-github about the asynchronicity problem, can't you let the user decide on a specific amount of time (interval) to wait before every action? |
Perhaps make it possible to have each action only happen after a specific key is pressed (which would act as a "step to the next action"). Macros would be a fantastic addition! |
Would it be possible to use "q" to record a macro, and invoke it, just like in vim?
The text was updated successfully, but these errors were encountered: