Capture and monitor LSP logs
watchlogscommandsetup L2★3
webspam/witcherscript-language ↗What it does
Stream LSP server stderr with line limit
Best for
Debugging LSP editor integration when client-side requests (completions, hover) behave unexpectedly.
Inputs
- · port (optional)
- · line count (optional)
- · scenario hint (optional)
Outputs
- · streamed LSP stderr
- · LSP activity report
Requires
- · LSP server binary
- · just recipe runner
Preconditions
- · witcherscript LSP project initialized
- · just recipe available
Failure modes
- · LSP startup slow → longer wait for banner
- · log file truncated → tail continues beyond N lines
- · no client connect → report server ready anyway
- · ANSI codes in log → sed strips or config disables
Trust signals
- · Banner-based startup detection (not timing)
- · Line-count cap via awk NR
- · ANSI-escape stripping documented
- · Log file preserved for full review