-
Notifications
You must be signed in to change notification settings - Fork 9
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
Migrate python-commands to vimscript commands #3
Comments
This is currently in progress on a different repository: Vigor. Once Vigor supports all of the commands that V does, I will merge the two back together. |
why use separate repo and not branch |
|
Everything is done! All logic, operators, motions, new commands, mappings, etc. are now implemented purely from within neovim! And beyond that, a ton of bugfixes, new operators and new features were added. I'm really happy about this particular milestone. Up next on the chopping block is better UTF-8 support, then after that maybe some more math. |
@DJMcMayhem +100 10/10 for less python :P |
It's not about removing python, it's about having it in a state where adding new features is actually remotely possible. I'm going to add more python down the road. |
Currently, commands are implemented in python. This is a big problem since python doesn't have full access to the state of vim when the command starts. The simple obvious solution is to replace all of the python commands with vimscript commands. That will allow the python code to be simplified, since we won't need to track things like mode, and count.
The text was updated successfully, but these errors were encountered: