diff options
| author | Gabriel Schneider <[email protected]> | 2026-09-30 12:10:51 -0300 |
|---|---|---|
| committer | Gabriel Schneider <[email protected]> | 2026-10-01 00:12:17 -0300 |
| commit | e27ec50ecad669a21b33c2c2e7c591828ba97e1b (patch) | |
| tree | 384da9de703616a9e1aca3480dbf9c6f189b9794 /src/detached | |
| parent | 996f4d256b95134b0b3d0fc8e8b558792f8f6c61 (diff) | |
| download | pardes-e27ec50ecad669a21b33c2c2e7c591828ba97e1b.tar.gz pardes-e27ec50ecad669a21b33c2c2e7c591828ba97e1b.zip | |
Lspwhy explains the last language server query asked, its kind, argument and place, not always a definition at the cursor
Lspwhy said it explains how the last request was answered, but it always
replayed a definition query at the current cursor. So after a failed Hover
it narrated a gd somewhere else, which told nothing about the failure.
Now the core remembers the last query (kind, argument, pane, offset), and
Lspwhy sends it as `<kind> <arg>`, at the query's offset when asked from
the same pane. The client narrates that kind: lsp.explaining reads it, and
the heading names it ("the hover query at byte N"). With nothing asked yet
it is a definition, as before. The effect's arg grows to 160 bytes so a
128-byte argument fits with its kind.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Diffstat (limited to 'src/detached')
0 files changed, 0 insertions, 0 deletions
