-
Notifications
You must be signed in to change notification settings - Fork 119
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
New shell waits for the Enter key press before showing prompt #552
Comments
Yea I'm getting the same issue. No prompt until I press enter, run a command, or clear (Ctrl+L). Seems like @IlanCosman has abandoned this project, which is a shame. They haven't touched anything here since February 2024, and they have recent activity elsewhere in GitHub. Time to get used to something else, I guess. |
@durad Check if you have pure installed. I had it installed via the package cachyos-fish-config. After removing it and reinstalling tide, the issue went away |
I take that back. It works fine with Fish 3, but I get that issue again when upgrading to Fish 4, even after reconfiguring tide |
My workaround with removing the parameter actually doesn't do anything (it doesn't configure Tide at all, just prints the error) so I'm guessing the workaround would be to completely remove |
@Gelmo You mentioned that you're having the issue with Fish 4. I'm curious, what does your config.fish looks like? Do you have |
@durad |
Yes, I know you can use it to run interactive configuration. However you can also use it with parameters as a cli command only. If you look at my first video that is what I had in my |
@durad Ha! I totally misunderstood you message, sorry! Here's my config:
|
@Gelmo No problem and thanks for looking into this! I guess since Tide stores all of its configuration in universal vars we can just go ahead and remove |
Describe the bug
When opening Fish shell with Tide inside certain applications (VS Code, ssh) shell hangs and waits for the Enter key press.
Steps to reproduce
In VS Code
Expected:
Actual:
With SSH
Expected:
Actual:
Screenshots
If I open a new Fish shell in VS Code prompt wouldn't show until I press enter:
Screen.Recording.2024-12-21.at.9.17.33.PM.mov
When running an SSH to a machine with Fish and Tide same thing happens:
Screen.Recording.2024-12-21.at.9.24.07.PM.mov
I found a simple workaround to this issue - remove one of the parameters in
tide configure ...
like--show_time=No
. This will cause an error message in a new shell but this can be fixed withtide configure ... > /dev/null
:Screen.Recording.2024-12-21.at.9.27.13.PM.mov
When SSH-ing into remote machine this workaround will also prevent clearing of terminal which I found useful:
Screen.Recording.2024-12-21.at.9.30.51.PM.mov
Environment
Output of
tide bug-report
:Additional context
Screen captures are showing Fish greeting as I tried to keep the config down to a minimum, but same happens when greeting is removed.
When using SSH to remote to a machine with Tide screen gets cleared. I'm not sure if this is by design, but since the same workaround of not including a tide parameter is fixing it (or breaking it), it is worth mentioning it. It would be great if the terminal is not cleared when SSH-ing to a different machine.
The text was updated successfully, but these errors were encountered: