[a-team-app]

Summary

Quick info (Ctrl+G I, gi, Go › Quick info, right after Go to definition) asks the file's language server what the name under the caret is and shows it in a box just under the line, or above it near the bottom of the editor: the signature coloured with the file's grammar, then the doc comment wrapped.

• Esc closes it and leaves the caret where it was. Enter closes it and goes to the definition, as gd does. ↑ ↓ PgUp PgDn scroll a long answer. Any other key closes it and goes on to the editor, so typing x inserts x.
• Its buttons sit on its bottom border, Enter Go to definition and Esc Close, and clicking one does what its key does. F1 while it's open lists its keys and leaves it open.
• With no answer it says Nothing to show here. While the server is loading or missing it says so exactly as gd does, and the menu item is dimmed until the server is ready. If you press it twice quickly, only the second answer shows.

Closes #591

Choices beyond the task

• The buttons are right-aligned, with the main action first (Enter Go to definition, then Esc Close). The style guide's dialog rule puts them in that order, where the pitch mockup had them on the left and the other way round.
• On a narrow editor the button labels get shorter: first Enter Definition, then just Enter and Esc, so the buttons never overflow the box.
• Prose wraps at 80 columns, or as wide as the signature if that's wider. Otherwise a long doc comment would stretch the box across a wide editor.
• Markdown is only partly cleaned up. Rules (---), backslash escapes and the backticks around inline code are removed. Everything else shows as written.
• A click, a scroll or a terminal resize that moves the caret closes the box, since it would no longer point at the name.

Notes for review

• I tried it with csharp-ls in a real terminal through tuirec: the box shows below the line and above it near the bottom; Esc, typing, →, Enter, both button clicks and F1 all work; and at 58 and 70 columns the box still fits and draws cleanly. I didn't try it with a Python or TypeScript server, because none is installed here. The parser covers every hover shape those servers send (MarkedString, arrays of them, MarkupContent), and the tests cover each one.
• IInputScopeStack gains Top. LayeredScope gains an optional callback for keys it passes on. The chat's code colouring moved into CodeBlockColours so the box can share it.

a-team try tuicode 595

🤖 Generated with Claude Code