eulix-lsp

I wrote eulix-lsp to serve libeulix's knowledge base over the Language Server Protocol, so one server gives an editor outline, go-to-definition, references and call hierarchy for nine languages.

Status
◐ Beta
Year
2026
Stack
Rust · LSP · tower-lsp · libeulix
Source
Nurysso/eulix/tree/main/eulix-lsp
13
editor features
9
languages

01 / Overview

What it does

eulix-lsp is a language server built on libeulix. It supports C, C++, Go, Java, JavaScript, PHP, Python, Rust and TypeScript, and serves symbols, go-to-definition, references, hover, completion, call hierarchy, semantic tokens and workspace diagnostics from libeulix's knowledge base. It leaves out what it cannot back up instead of guessing.

02 / Usage

Build it, point your editor at it

Build
cargo build --release
Run
./target/release/eulixlsp    # point your editor's LSP client at this binary

03 / Features

What it does

  • Navigate

    Document outline, go to definition across files, workspace-wide references, same-file highlights, workspace symbols and folding ranges.

  • Read

    Hover shows the signature, docstring and complexity. Semantic tokens are symbol-level and delta-encoded.

  • Write

    Prefix-filtered completion ranked by proximity. Rename refuses when the name is ambiguous in the workspace.

  • Call hierarchy

    Incoming and outgoing calls, taken from libeulix's call graph.

  • Diagnostics

    Syntax errors, duplicate definitions, TODOs and security notes across the workspace, with a file watcher that picks up changes on disk.

04 / Scope

Left out on purpose

  • No code actions or formatting

    There is no signature help either. The parse result does not carry what they need, and inventing it would be guesswork.

  • No type hover

    Hover shows what the parser extracted. It does not resolve types through assignments or calls.

  • One definition target

    When a name has several definitions, the closest wins. Find references lists them all.

  • Rename edits open buffers

    Closed files are left alone, because a precise edit needs the file text and a guessed whole-line edit would be worse than skipping it.

  • Prefix completion only

    There is no fuzzy matching and no ranking beyond proximity and sort order.

  • Symbol-level tokens

    Every name the parser extracted gets a token. The rest of the file keeps the editor's own highlighting.

05 / Install

Get it running

From source
git clone https://github.com/Nurysso/eulix.git && cd eulix/eulix-lsp && cargo build --release

Needs Rust stable and a C compiler. It is not on crates.io, so build it from source, then point your editor's LSP client at the binary.

06 / Limits

Rough edges

  • Beta. It only offers what the parse result can back up, so there are no code actions, formatting, signature help or type hover.
  • Rename only edits open buffers, and go-to-definition returns one target.
  • JSX and TSX are not supported, and syntax diagnostics are per line, not per error.

07 / FAQ

Before you try it

Which editors work?
Any editor with an LSP client. Point it at the built binary.
Why are there no code actions or formatting?
The parse result does not carry what they need, and inventing it would be guesswork.
Does rename change files I have not opened?
No. Rename only edits open buffers. The reverse index gives the file and line of each call site, but a precise edit needs the file text, so closed files are left alone.
Why does go-to-definition give one result?
When a name has several definitions, the server picks the closest: same file, then same directory, then shortest path, then lexicographic. Find references lists them all.
Does it work with JSX and TSX?
No. libeulix detects them but has no parser for either, so the server leaves them out instead of offering features it cannot back up.

eulix-lsp

I wrote eulix-lsp to serve libeulix's knowledge base over the Language Server Protocol, so one server gives an editor outline, go-to-definition, references and call hierarchy for nine languages.