mirror of
https://github.com/Myriad-Dreamin/tinymist.git
synced 2025-07-07 21:15:03 +00:00
![]() * feat: declare and bind tinymist.profileServer command * feat: editor bridge with the frontend * feat: start and stop server profiling * feat: add profile-server prototype (#1440) * Add profile-server prototype * fix: use branch --------- Co-authored-by: Myriad-Dreamin <camiyoru@gmail.com> * feat: make it good * build: update cargo.lock * dev: ls profile impl and hook * test: update snapshot --------- Co-authored-by: Derived Cat <hooyuser@outlook.com> |
||
---|---|---|
.. | ||
src | ||
Cargo.toml | ||
README.md |
sync-ls
Sync LSP server inspired by async-lsp, primarily for tinymist. The author of this crate thinks that async-lsp is better than sync-ls, so please use async-lsp whenever possible unless you have a good reason to use sync-ls. Some random points:
- The
req_queue
andtransport
are extracted from the rust-analyzer project. - The sync-ls should have better performance on stdio transport than async-lsp, especially on windows, but the author have forgotten the idea.
- The sync-ls handlers can get a mutable reference to the state, which is not possible in
tower-lsp
. - The sync-ls supports both LSP and DAP with a common codebase.
Debugging with input mirroring
You can record the input during running the editors with binary. You can then replay the input to debug the language server.
# Record the input
your-ls --mirror input.txt
# Replay the input
your-ls --replay input.txt
This is much more useful when devloping a dap server.
Usage
Starts a LSP server with stdio transport:
with_stdio_transport::<LspMessage>(args.mirror.clone(), |conn| {
let client = LspClientRoot::new(tokio_handle, conn.sender);
LspBuilder::new(args, client.weak())
// Adds request handlers
.with_request::<Shutdown>(State::shutdown)
// Adds event handlers
.with_event(&LspInterrupt::Settle, State::interrupt)
.build()
.start(conn.receiver, is_replay)
})?;