-
Notifications
You must be signed in to change notification settings - Fork 4
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
Characters not echoing after after using autocomplete #1
Comments
Good morning and thank you for looking into I confirm that with I would be inclined to think that the responsibility lies in the library I am using to show the prompt, namely go-prompt and the way it passes the exit codes to the shell (I have re-created a minimal prompt example independent of Just for reproducibility sake: could you report the specific of the system you are using (terminal, shell, operating system)? |
I have reproduced the issue by copying and pasting the documentation example: see below Screen.Recording.2021-07-07.at.10.57.03.movso the problem is indeed the way Please validate that this is the case on your hand too and if so we can open an issue there and reference this one for completeness. |
I could also reproduce the bug by running the dependency's provided examples. I looked into the project and it appears this issue has already been reported in c-bata/go-prompt#228, c-bata/go-prompt#233 and a fix is provided by c-bata/go-prompt#239. It may be nice to integrate as a patch. |
So it seems that the PR is waiting to be merged. I would say we wait for the merge so that I can re-release |
Yes -- for those that want an immediate fix: if you do |
The PR has been merged, I am closing this as the issue should be fixed. |
Hello, I am the maintainer for the element package on NixOS!
I noticed that after using autocomplete, characters do not echo on the command line after the program exits. The only way known to me to fix this is by executing
reset
. This happens when using regularbash
andbash --posix
.I've included an asciinema demonstrating the problem. Unfortunately I'm not familiar with Go, so I can't provide a PR, but I'd love to see a fix for this program!
The text was updated successfully, but these errors were encountered: