RunLogosRunLogos
中文EN

IDE Partial Setup Guide

When the RunLogos source editor shows IDE Partial, TypeScript / JavaScript or some language services are usually already available, while one or more project language servers are missing, not visible to the GUI process, or detected but not started yet. This page explains how to install and troubleshoot language services for Python, Go, Rust, and Java.

What IDE Partial Means

RunLogos detects language services from the current project and shows an overall IDE status in the editor status bar:

StatusMeaning
IDE ReadyThe language services required by the current project are running and can provide diagnostics, completion, navigation, and related features
IDE PartialSome language services are available, while others are missing, stopped, or need a fresh detection
IDE OfflineNo language service is currently available, or the status query failed

Each language can also show a more specific status:

StatusMeaningNext step
readyThe language service is running and can handle requestsUse it directly
availableRunLogos detected the language server, but it is not currently runningClick Restart / Start
unavailableRunLogos did not detect the language serverInstall the runtime or LSP, then click Redetect

The built-in RunLogos panel keeps only short hints, current diagnostics, and quick actions; even when offline, it still tells users the next step. The website carries the full install guide, platform-specific commands, common PATH locations, and troubleshooting steps.

Python / Pyright

Python semantic features are provided by Pyright. RunLogos detects the pyright-langserver executable.

ItemDetails
Required runtimeNode.js / npm
LSPpyright-langserver
RunLogos actionsCopy command, redetect, Restart / Start
Common macOS paths/opt/homebrew/bin, /usr/local/bin
Common Windows paths%APPDATA%\npm

macOS:

npm install -g pyright
pyright-langserver --version

Windows:

npm install -g pyright
pyright-langserver --version

If the status still shows available after installation, click Restart / Start. If it still shows unavailable, check the global npm bin directory from npm config get prefix, add it to the system PATH, and restart RunLogos.

Go / gopls

Go semantic features are provided by gopls. Install the Go toolchain first.

ItemDetails
Required runtimeGo toolchain
LSPgopls
RunLogos actionsCopy command, redetect, Restart / Start
Common macOS paths~/go/bin
Common Windows paths%USERPROFILE%\go\bin

macOS:

go version
go install golang.org/x/tools/gopls@latest
gopls version

Windows:

go version
go install golang.org/x/tools/gopls@latest
gopls version

If go is missing, install Go first and confirm go version works. If gopls is missing, run the install command, add ~/go/bin or %USERPROFILE%\go\bin to PATH, then click Redetect.

Rust / rust-analyzer

Rust semantic features are provided by rust-analyzer. Installing it through rustup is recommended.

ItemDetails
Required runtimerustup / Rust toolchain
LSPrust-analyzer
RunLogos actionsCopy command, redetect, Restart / Start
Common macOS paths~/.cargo/bin
Common Windows paths%USERPROFILE%\.cargo\bin

macOS:

rustup --version
rustup component add rust-analyzer
rust-analyzer --version

Windows:

rustup --version
rustup component add rust-analyzer
rust-analyzer --version

If rustup is missing, install the Rust toolchain first. If the component is unavailable, confirm the current toolchain is installed and usable, run rustup update, then retry.

Java / Eclipse JDT LS

Java semantic features are provided by Eclipse JDT LS. RunLogos does not automatically install JDT LS; it only provides the guide, copyable commands, and path hints.

ItemDetails
Required runtimeJDK
LSPEclipse JDT LS / jdtls
RunLogos actionsCopy command, redetect, Restart / Start
macOS recommendationInstall with Homebrew, or install JDK + JDT LS manually
Windows recommendationInstall JDK and JDT LS manually, then add the jdtls directory to PATH

macOS:

java -version
jdtls --version

Windows:

java -version
jdtls --version

If jdtls --version is not available, install a JDK first, then install Eclipse JDT LS and add the jdtls directory to PATH. JDT LS uses workspace / cache directories for indexes and project state; those directories should not be committed to the repository.

How To Make RunLogos Detect The Installation

Use this order:

  1. Verify the command in a terminal, for example gopls version, pyright-langserver --version, rust-analyzer --version, or jdtls --version.
  2. Return to the RunLogos IDE Language Services panel and click Redetect.
  3. For languages with available status, click Restart / Start.
  4. If the language server is still not visible, fully quit and reopen RunLogos so the GUI process reads the updated PATH.
  5. On macOS, check /opt/homebrew/bin, /usr/local/bin, ~/go/bin, and ~/.cargo/bin.
  6. On Windows, check %APPDATA%\npm, %USERPROFILE%\go\bin, and %USERPROFILE%\.cargo\bin.

Do not send License Keys, project source code, prompts, environment secrets, or private repository content to AI or commit them to a repository. Troubleshooting language services only needs command names, versions, PATH values, and the RunLogos status.

Common Errors

ErrorMeaningHow to fix
package-manager-missingnpm, go, rustup, or another installer is missingInstall the required runtime first, then retry the LSP installation
network-unavailableThe package manager cannot download dependenciesCheck network access, proxy settings, or mirror configuration
permission-deniedThe global install directory is not writableUse a user-level install directory, or fix directory permissions
post-detect-failedRedetect still fails after installationCheck whether PATH is visible to the GUI process, then reopen RunLogos
lsp-start-failedThe executable exists but the language server failed to startRun the version command in a terminal and confirm the runtime and dependencies are complete
LSP exited with code 127The process could not find a binary or runtime dependency when startingCheck PATH, runtime installation, and differences between shell and GUI environments first

If the command works in a terminal but RunLogos still cannot see it, the usual cause is a mismatch between terminal PATH and GUI PATH. Add the corresponding bin directory to the system-level PATH, fully quit RunLogos, and open it again.

-> Back to IDE Language Features