-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
bash shell does not echo typed characters #1503
Comments
I have the same problem, it seems to be introduced in Poetry 1.0.0b2 I can workaround it by blindly typing |
Thirding this problem. The bug is present in various Bash terminals, including the PyCharm one. Poetry 1.0.0b3 on Ubuntu 18. I can confirm the reset workaround, as well. |
Did a bit of debugging... seems like a timing issue. In
Removing Edit: I'm running poetry 1.0.0b3 on macOS 10.14.6 Mojave |
Ping @sdispater about removing that sentence or delaying its execution a bit. |
Also experiencing this problem with:
|
Also experiencing this with:
|
The problem no longer occurs for me with Poetry 1.0.0b8, so it looks like the fix is working. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Issue
The
poetry shell
command worked fine on my machine for Poetry 0.12.17, but after upgrading to Poetry 1.0.0b3, when I get the shell prompt after running thepoetry shell
command, the terminal output is broken. The most striking problem is that characters I type are not echoed, but there are other output glitches as well:At this point, I can type commands and they are executed, but I don't see any of the characters I type echoed after the prompt. After running
reset
my typed input is echoed again.Note the missing newline at end: that is not a copy-paste error, that actually happens in the terminal. When I execute a command like
ls -1
, the newline from typing the command does not appear, but the newlines printed byls
do:I thought the problem might have to do with the ANSI codes used to produce colors, but while
poetry shell --no-ansi
does suppress the color output, it doesn't fix the problem.The problem is specific to bash: if I start a different shell, it works fine:
I have a git prompt and several completions configured for bash on my normal developer account, so to rule out that those are causing problems I created a new user account and disabled the systemwide bash configurations by renaming the
/etc/aliases.d
,/etc/bash_completion.d
and/etc/profile.d
directories. That didn't fix the problem.I tried changing the
TERM
environment variable fromxterm-256color
to justxterm
and tovt100
, but that didn't fix the problem either.At this point I'm out of ideas for what else I could be trying to diagnose this problem. If anyone has a clue, please comment.
The text was updated successfully, but these errors were encountered: