fwcd / fwcd/kotlin-language-server
How to display more of the documentation for system libraries?
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 2k
- Forks
- 252
- PR merge metrics
- No merged PRs in 30d
Description
Hi I'm new to LSPs so not sure where exactly to ask this question.
I'm trying to get kotlin LSP to show more of the documentation like how Intellij does, any pointers on how can I go about doing that?

Currently using it in neovim with it's native LSP + kotling-language-server but I don't see the complete doc like shown above.

Current config:
◍ kotlin_language_server
version 1.3.1
installed 21 Jul 2022 18:45
install dir ~/.local/share/nvim/lsp_servers/kotlin
homepage https://github.com/fwcd/kotlin-language-server
↓ Server configuration schema (press enter to collapse)
This is a read-only representation of the settings this server accepts. Note that some settings might not apply to neovim.
For information on how to customize these settings, see :help lspconfig-setup
→ kotlin.compiler.jvm.target default: "default"
→ kotlin.completion.snippets.enabled default: true
→ kotlin.debounceTime default: 250
→ kotlin.debugAdapter.enabled default: true
→ kotlin.debugAdapter.path default: ""
→ kotlin.externalSources.autoConvertToKotlin default: false
→ kotlin.externalSources.useKlsScheme default: true
→ kotlin.indexing.enabled default: true
→ kotlin.java.home default: ""
→ kotlin.languageServer.debugAttach.autoSuspend default: false
→ kotlin.languageServer.debugAttach.enabled default: false
→ kotlin.languageServer.debugAttach.port default: 5005
→ kotlin.languageServer.enabled default: true
→ kotlin.languageServer.path default: ""
→ kotlin.languageServer.port default: 0
→ kotlin.languageServer.transport default: "stdio"
→ kotlin.linting.debounceTime default: 250
→ kotlin.snippetsEnabled default: true
↓ kotlin.trace.server default: "off"
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the kotlin_language_server entry point for LSP documentation responses and Neovim's native LSP handling of them. Compare the current output with the IntelliJ example; done means system-library documentation is displayed as completely as in the example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, neovim
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100