Skip to content

Comments

fix: forward logs through window log handler#418

Open
mkaput wants to merge 1 commit intoelixir-lang:mainfrom
mkaput:mkaput/window-log
Open

fix: forward logs through window log handler#418
mkaput wants to merge 1 commit intoelixir-lang:mainfrom
mkaput:mkaput/window-log

Conversation

@mkaput
Copy link
Contributor

@mkaput mkaput commented Feb 20, 2026

Add a centralized logger-to-LSP bridge for window/logMessage instead of ad hoc GenLSP.log/info/error calls. This routes operational logs through one path and keeps window/showMessage for explicit errors.

Implement Expert.Logging.WindowLogHandler with runtime attachment, recursion guards, OTP/SASL/report filtering, and OTP 25/26+ compatibility via Expert.Logging.LoggerHandler. Wire attachment during app boot and test bootstrap, and route engine init events to lsp.pid so non-default test servers receive them.

Add client-based gating for Emacs/Eglot in configuration (issue #382 workaround), plus tests covering config behavior, handler idempotency/replacement, and Emacs suppression semantics.

fix #382

CleanShot.2026-02-20.at.14.20.26.mp4

Add a centralized logger-to-LSP bridge for window/logMessage instead of ad hoc GenLSP.log/info/error calls. This routes operational logs through one path and keeps window/showMessage for explicit errors.

Implement Expert.Logging.WindowLogHandler with runtime attachment, recursion guards, OTP/SASL/report filtering, and OTP 25/26+ compatibility via Expert.Logging.LoggerHandler. Wire attachment during app boot and test bootstrap, and route engine init events to lsp.pid so non-default test servers receive them.

Add client-based gating for Emacs/Eglot in configuration (issue elixir-lang#382 workaround), plus tests covering config behavior, handler idempotency/replacement, and Emacs suppression semantics.

fix elixir-lang#382
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Log more with window/logMessage

1 participant