Open its-all-waves opened 5 months ago
At present, there are still many details that need to be corrected in Inkdown. Vim motions may not currently support it. Perhaps will consider adding this feature during the relatively complete and stable period of Inkdown. Unfortunately
If/when you consider this again:
Consider seeing how much behavior you can import from the VSCode Vim plugin?
I haven't done any VS Code extension development, so I don't really know if this is reasonable or utterly infeasible, but between these options:
There's a decent chance that option 2 or 3 would be a much greater payoff for less effort than option 1.
Then again, option 4 might work too ;)
If/when you consider this again:
Consider seeing how much behavior you can import from the VSCode Vim plugin?
I haven't done any VS Code extension development, so I don't really know if this is reasonable or utterly infeasible, but between these options:
- Implement parts of vim yourself
- Implement enough of the VSCode plugin API to use the vim plugin
- Fork the VSCode vim plugin to replace the vscode dependencies with your own
- Maybe there's another vim-motion npm module I haven't noticed
There's a decent chance that option 2 or 3 would be a much greater payoff for less effort than option 1.
Then again, option 4 might work too ;)
Thank you for your suggestion. However, as a text editor, inkdown is different from the underlying principle of vscode and cannot be directly reused vim plugin. Adding a feature requires a lot of testing to stabilize, So this feature may be added in the future and is currently not supported.
Oh, I'm not suggesting you'd be able to directly reuse the plugin, but it might be easier to adapt it than implement vim motions from scratch.
I totally understand it being way down at/below the bottom of the roadmap, keep up the good work!
I'm loving this application and I'm frankly amazed that this is the first of its kind!
It would be nearly perfect if it had Vim motions. I don't think I need to explain the benefits. Thank you!