panache-lsp(1)

💅 panache-lsp(1) — the manual page, but make it make sense

bestie, you're looking at panache-lsp from the General Commands Manual — it's the little server that makes your editor ✨understand✨ Panache. Let's get into it 🫶

---

✨ NAME ✨

panache-lsp — start the Language Server Protocol server 👑 no cap, that's literally the whole job.

---

🌸 SYNOPSIS 🌸

panache lsp [--debug] [-h|--help] [-V|--version]

that's it. that's the whole command. iconic behavior honestly 🎀

---

🦋 DESCRIPTION 🦋

okay so boom: this starts the Panache language server protocol (LSP) server, which is the thing that hooks you up with editor integration 💖

the LSP server gives formatting capabilities to editors like VS Code, Neovim, and literally any other editor that supports LSP. so like, your editor gets the good good formatting powers. slay 🌈

---

💅 OPTIONS 💅

• --debug — turns on verbose LSP debug logging 📝 the log goes to ~/.local/state/panache/panache-lsp-debug.log, or to $XDG_STATE_HOME/panache/panache-lsp-debug.log when XDG_STATE_HOME is set. and why file logging? because logs get written to a file specifically so they don't interfere with the LSP protocol over stdout 🧚 (the protocol is using stdout, so we are NOT gonna mess with it, periodt).
• -h, --help — print help (see a summary with -h) 🫶
• -V, --version — print version ⭐

lowkey important: the LSP server talks over stdin/stdout, and it's typically launched automatically by your editor's LSP client. so fr fr, you generally don't need to run this command manually 🙈

---

🍓 EXTRA 🍓

for editor configuration examples, go here (yes it's a link, yes it's the good stuff):

https://github.com/jolars/panache#editor-integration

---

🔥 VERSION 🔥

v3.16.0 — that's the one, bestie 💜

---

🎀 SEE ALSO 🎀

panache(1), panache-format(1), panache-parse(1), panache-lint(1), panache-clean(1), panache-debug(1)

like, the whole friend group 🫶✨

---

and that's a wrap, bestie 💖 this page is lsp 3.16.0 energy, filed under panache-lsp(1), and it ate. mwah 💋🎀