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

How hard do you think Language Server support would be? #65

Open
jcflack opened this issue Oct 12, 2021 · 1 comment
Open

How hard do you think Language Server support would be? #65

jcflack opened this issue Oct 12, 2021 · 1 comment

Comments

@jcflack
Copy link

jcflack commented Oct 12, 2021

I have really liked NEdit for something like 25 years. I love that xnedit finally solves the "but no Unicode" problem and I can still build it in 21 seconds and it's 1.6 MB and starts up instantly.

But I also really like this newfangled Language Server Protocol idea. Factor language-sensitive support out into an external process with a standard protocol. A bunch of future issues for "please add highlighting for language X" could turn into "look, there's already language server support for language X".

It wouldn't be worth it if xnedit would have to stop being small and nimble. But if it could be added without too much bloat? That could be really cool.

It looks like vim8 and neovim have already taken the plunge.

@unixwork
Copy link
Owner

I have already looked at LSP and I'm planning to implement it. Obviously it will be some work, but it is doable.

It wouldn't be worth it if xnedit would have to stop being small and nimble.

I don't think bloat will be a problem. Also, I really care about startup time. I need a texteditor that starts immediately.

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