Repository navigation
Debugger => Some variable content popup issues #1628
Description
Activity
Hi reuschling, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.
Workarounds & Suggestions
- Copy full value: In the Variables view right-click your variable → Copy Value (Ctrl+C) or Copy as Expression, then paste into an editor to see the full multiline content.
- Enable sticky hovers: In your settings.json add:
This lets you move your mouse into the hover popup without it disappearing immediately.
"editor.hover.sticky": true
- Use Debug Console: Evaluate or
print(variable.toString())in the Debug Console to get a full, scrollable, multiline result.
Existing Feature Request
- Is there a way to see the full toString() content of a variable, including newlines? (#1111) – you can add a comment or 👍 to upvote this enhancement for multiline hovers and native
toString()expansion.
Other references with low confidence
- hover instance in debug mode don't show popup with details (#444) – reports hover popups not appearing at all after an update.
The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!
The AI labeled this as enhancement, which is only partially true
reuschling Thanks for the detailed feedback. I agree this is a valid usability issue for long or multiline variable values.
Most of the behavior mentioned here is controlled by VS Code's debug/editor UI rather than the Java debugger extension. The Java
extension can provide the variable text /toString()value, but hover positioning, stickiness, selection, scrolling, and actions
inside the popup are handled by VS Code. The lazy “click to expand” action is currently only supported in the VARIABLES tree, not in
inline value or hover popups.So I’d keep this as an enhancement / upstream-dependent issue. Current workarounds are enabling
"editor.hover.sticky": true,
setting"java.debug.settings.maxStringLength": 0, or evaluatingvariable.toString()in the Debug Console / WATCH view.
During debugging, VsCode has three quick possibilities to show the detailed content of variables (as far as I know):
I have found these issues with it: