-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[2024.10.2] Terminal rendering issue with long text when using input() #2246
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
Comments
If you change
I can't estimate the effort right now as the repl, or input logic, is pretty different (ad-hoc in MicroPython, starting from its core abilities, delegated to readline in Pyodide) @ntoll any thought around it? I think I might personally be happy to ditch readline dependency as a whole at this point, as recently it's causing more issues than it solves (but it's been very keen and nice to solve at least some issue we filed in there). |
Feels like it'd be good to do some discovery to better estimate the effort to address this in a way that we can prioritize compared to other things that are lined up... |
pyodide terminal adds a horizontal scroll bar for long text. Is it possible to add a horizontal scroll bar to the terminal instead of extending to next line? |
@nasrin1748 please let's not add requests within an issue that's unrelated ... we need to fix it in a way that works like a terminal (no horizontal scrolls on a terminal, since its first appearance) ... requests should find their place in discussion with proper reasons, use cases, and whatnot, thanks. |
Published (until release) as |
Uh oh!
There was an error while loading. Please reload this page.
Checklist
What happened?
When using a long string together with input(), if the text overflows because there is not enough space, the line shows in the terminal twice.
PyScript.com project to reproduce: https://pyscript.com/@joshualowe1002/sparkling-scene/latest?files=main.py
What browsers are you seeing the problem on? (if applicable)
No response
Console info
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: