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

Add support for ink-language-server #2683

Merged
merged 1 commit into from
Sep 22, 2019
Merged

Add support for ink-language-server #2683

merged 1 commit into from
Sep 22, 2019

Conversation

ahayworth
Copy link
Contributor

Add support for ink-language-server

This commit add support for ink-language-server, which it does by
largely copying and pasting from the pure-language-server PR that was
merged recently.

The most interesting things to note are:

  • ink-language-server is distributed upstream via npm, which is why we
    search through node_modules
  • With some coaxing, it can be installed globally - which is why we
    search for a global binary.
  • Ink is a funky language, and users will likely need to add
    initialization options.
  • I am not incredibly familiar with vimscript; and I may not have done
    some of the buffer searching correctly.

NB: Some of the formatting tests failed for me on both master, and my feature branch. Given that they fail both places, I've decided to make this PR anyways. But, if something in this commit did break tests, I'm happy to fix them of course.

This commit add support for ink-language-server, which it does by
largely copying and pasting from the pure-language-server PR that was
merged recently.

The most interesting things to note are:
- ink-language-server is distributed upstream via npm, which is why we
  search through node_modules
- With some coaxing, it can be installed globally - which is why we
  search for a global binary.
- Ink is a funky language, and users will likely need to add
  initialization options.
- I am not incredibly familiar with vimscript; and I may not have done
  some of the buffer searching correctly.
@ahayworth ahayworth closed this Aug 8, 2019
@ahayworth ahayworth reopened this Aug 8, 2019
@ahayworth
Copy link
Contributor Author

Hi there - is there anything I can do to help get this reviewed and/or merged? Completely understand if things are just busy and this is on the backburner, but I want to make sure it's not waiting on something else from me. 😄

@w0rp w0rp merged commit 6746eae into dense-analysis:master Sep 22, 2019
@w0rp
Copy link
Member

w0rp commented Sep 22, 2019

Thanks for this, and sorry for the delay. I've just been slowly going through a backlog of emails.

Cheers! 🍻

@ahayworth
Copy link
Contributor Author

No problems at all! I can imagine this project takes a lot of your time. Thank you for taking the PR, and thanks for this awesome project!

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

Successfully merging this pull request may close these issues.

2 participants