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 details on how to use this LSP for non-Atom editors #27

Merged
merged 1 commit into from
Dec 29, 2020

Conversation

jo-sm
Copy link
Contributor

@jo-sm jo-sm commented Dec 29, 2020

This PR clarifies how to setup racket-langserver for IDEs that don't necessarily have a package for it.

I recently setup racket-langserver in Sublime after looking up how to add a custom client and following the simple instructions in #21 (comment), so I figure it makes sense to put them in the README for others to more easily see.

I also moved the code formatting section into Currently Supported since as far as I can tell support has been added now (#24).

Do y'all have any thoughts on a troubleshooting or additional info to add here, and if so, what would go in there? Is there a minimum version you should have for the package? My Racket is at 7.9 but I saw in the comment linked above someone may have issues if they have an older version, so it might be good to add to the README as well.

- Move code formatting to Currently Supported section
@jeapostrophe jeapostrophe merged commit 68206e3 into jeapostrophe:master Dec 29, 2020
@jeapostrophe
Copy link
Owner

This is great. Thank you. I don't believe that there are any big version pre-reqs, because I think we're relying on fairly "old" Racket APIs. If people find examples of combinations that are broken, then the best thing to do is add a requirement in info.rkt at the Racket level and then raco will complain. Better still we could add version exceptions to the package server so that raco will find the correct version.

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