-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
REPL completion completely broken on dot continuation on 2.13 #10914
Comments
That does not look like something is broken.
Could this issue just be closed? 😄 |
The representation leaves something to be desired, but this is an example of hitting
So no, it's not closable. |
Maybe the bad caret is a clue for a good first issue solver. The caret is like totally wrong. |
Thank you for clarifying! I'll look into this. |
Short update: I have implemented a fix for this this issue locally, and a related one I found during manual testing (tab expansion in dot-continuation wasn't working correctly in multiline input; which seams to be an old bug because it is reproducible in the old Scala 2.11.12 release; I didn't look for an related issue in the bug tracker until now but it's on the list). I still have to write tests. Also I'm looking currently whether I implemented the fix in the right place. But have first to grok how the interpreter is actually working. I'll submit a pull request for this issue soon. |
Hey @MateuszKowalewski, any update on this? |
@julienrf I just had not enough spare time to finish this lately. I'm quite sorry about this! Tests are still missing. The fix as it is works and was implemented already in the right spot (as far as I can tell after I had a deeper look into the inner workings of this thing). I'll try to add the tests and submit a pull request in the next days. Sorry once more for this very long delay. I thought that I have plenty of time to play around with the Scala compiler as I first looked into this issue. But then I got occupied with some quite important things. |
Hey @MateuszKowalewski, don’t be sorry! If you want you can already push your work to your fork and maybe someone from the community can help finishing it :) |
@MateuszKowalewski Feel free to PR what you have, I can follow up with a test. I am not occupied with any important things. |
@som-snytt I was about to finally get around to opening a ticket on this, only to discover it already exists |
@NthPortal Thanks again, for the nth time. I guess there was a reason it sounded familiar. |
this seems to have been gone away at some point, perhaps when we moved to JLine 3 |
The text was updated successfully, but these errors were encountered: