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.

Sign up for GitHub

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

Jump to bottom

support language server protocol #26

Open
prabirshrestha opened this issue Jan 2, 2017 · 1 comment
Open

support language server protocol #26

prabirshrestha opened this issue Jan 2, 2017 · 1 comment

Comments

@prabirshrestha
Copy link

Would you be interested in supporting the language server protocol server?

Currently I'm writing a lot of vim script and having language server protocol for vim script would be very useful for me.

Here is the language server protocol in plugin vim. https://github.com/prabirshrestha/vim-lsp
@prabirshrestha prabirshrestha mentioned this issue Jan 5, 2017
Closed
@haya14busa
Copy link
Member

Sounds really nice! 👍

I have no plan to work on language server protocol on my own at least for now,
because I'm not familiar with it and I'm somewhat busy to do other things.

I think you can use go-vimlparser to implement language server protocol for vim, so please feel free to use it.
I'm happy to help you if there are any missing feature in go-vimlparser to implement language server protocol.

@prabirshrestha prabirshrestha mentioned this issue Jan 8, 2017
Open
haya14busa added a commit that referenced this issue Nov 17, 2017
@haya14busa
Use s:TRUE/s:FALSE instead of 1/0
fc0bce5 
vim-vimlparser can be translated into Python and JavaScript which
convert number to boolean implicitly, but it's difficlut to translate it
into other language which doesn't have implicit type conversion.

I actually created translater to Go (ref: #26) by including this change.
(We need more tweak for Go translater, but this change is one of them)

Using s:TRUE/s:FALSE is better not only for translator, but also for
readability.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@prabirshrestha @haya14busa