jshell has unreadable javadoc on Git Bash

[David Alayachew]

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>
wrote:

> Hello @kulla-dev at openjdk.org <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/kulla-dev/attachments/20250602/6ddf711d/attachment-0001.htm>