jshell has unreadable javadoc on Git Bash

[Chen Liang]

Thanks for this report. I can reproduce this with the suggestions, it does print something that is hidden by user code. I created https://bugs.openjdk.org/browse/JDK-8365177 with the steps of reproduction, which I can reproduce on a linux machine too.



________________________________
From: compiler-dev <compiler-dev-retn at openjdk.org> on behalf of David Alayachew <davidalayachew at gmail.com>
Sent: Thursday, August 7, 2025 1:39 PM
To: compiler-dev <compiler-dev at openjdk.org>
Subject: Fwd: jshell has unreadable javadoc on Git Bash

Hello,

Since the kulla dev chat has just been retired, moving my unanswered question here instead. Please see the below thread, or let me know if I should copy paste it for easier reading.


---------- Forwarded message ---------
From: David Alayachew <davidalayachew at gmail.com<mailto:davidalayachew at gmail.com>>
Date: Mon, Jun 2, 2025, 8:57 PM
Subject: Re: jshell has unreadable javadoc on Git Bash
To: <kulla-dev at openjdk.org<mailto:kulla-dev at openjdk.org>>



Side note -- the same problem occurs in Commandline too for Windows 10. The only difference is that I can't use Shift+Enter to create the new lines. Instead, I did a .map(somePath -> {, and then pressed enter. The opening curly brace then allowed my enter to create a new line. After making a few new lines, then trying to press tab on a half-typed method, I got the same, garbled text.


And to be clear, they are garbled/interspersed, even on the same line.

On Mon, Jun 2, 2025, 8:52 PM David Alayachew <davidalayachew at gmail.com<mailto:davidalayachew at gmail.com>> wrote:
Hello @kulla-dev at openjdk.org<mailto:kulla-dev at openjdk.org> ,

I was using jshell to write some stream code today, and I was doing this in Git Bash on Windows 10.

I did list.stream(), then used Shift+Enter to create a new line for each method on my stream. Typical builder-style code formatting.

Then, I pressed Tab in order to see javadoc for one of the methods, and the resulting javadoc was basically illegible. It was a mix of the multi-line stream and the javadoc, jumbled together.

I think this is a bug? Can something be done to resolve this? Let me know if more information is needed.

Thank you for your time and consideration.
David Alayachew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/compiler-dev/attachments/20250808/b8dd2d38/attachment.htm>