Skip to content
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

Maybe use nvim as backend, or maybe implement LSP, ... #33

Open
dumblob opened this issue Sep 4, 2019 · 1 comment
Open

Maybe use nvim as backend, or maybe implement LSP, ... #33

dumblob opened this issue Sep 4, 2019 · 1 comment

Comments

@dumblob
Copy link

dumblob commented Sep 4, 2019

Don't know what are the goals of vid, but when I saw that vid wants to have some configuration (colors, ...), needs undo, wants non-vim controls, then I asked myself why not to save some work and use nvim as backend (as e.g. https://github.com/equalsraf/neovim-qt/ does)?

The performance shall be also very good, there are mature Emacs (or other controls "styles") plugins, etc.

Or vice versa - make vid stay a backend and just implement Language Server Protocol and use any frontend (graphical or console or whatever) you like.

^Just thoughts...

@medvednikov
Copy link
Member

I considered this.

I started this project as a proof of concept and to learn about editors.

Perhaps using existing backends is a good strategy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants