Skip to content

Conversation

mostalive
Copy link

…er itself

Attempt to resolve my own confusion as mentioned in issue #2, I had trouble finding the official LSP implementation after seeing a rumour about it earlier.

…er itself

Attempt to resolve my own confusion as mentioned in issue elixir-tools#2, I had trouble finding the official LSP implementation after seeing a rumour about it earlier.
Copy link

netlify bot commented Sep 16, 2025

Deploy Preview for expert-lsp-org ready!

Name Link
🔨 Latest commit fdd1fea
🔍 Latest deploy log https://app.netlify.com/projects/expert-lsp-org/deploys/68c9585ad118350008813b6a
😎 Deploy Preview https://deploy-preview-3--expert-lsp-org.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

# expert_lsp_org
# expert_lsp_org - Expert, Elixir LSP website

This is the impllementation of [expert-lsp.org](expert-lsp.org), the website for _Expert_, the [official Elixir Language Server Protocal server](expert-lsp.org). The [repository for the implementation of the Elixir LSP server](https://github.com/elixir-lang/expert](https://github.com/elixir-lang/expert) itself is at [https://github.com/elixir-lang/expert](https://github.com/elixir-lang/expert)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo detected.

Copy link

@BartOtten BartOtten Sep 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest to shorten the message and only include two hyperlinks. Both the website and the LSP server repo linked once instead of twice.

Here you find the code for the Expert LSP website.
Maybe you seek the code of the Expert LSP server.

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