-
Notifications
You must be signed in to change notification settings - Fork 308
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
psql makes spacing go weird #4484
Labels
Bugs
Bugs, Hangs, Crash, and Freezes
Comments
Hi @jpninanjohn This may be because Warp features like blocks arent supported in REPLS like psql. We already have a request tracking this over at #4082 If you could please give it a 👍 and subscribe to that request, it would help us gauge interest. We'll post any updates there, so stay tuned! We'll be closing this as a duplicate. |
Duplicate of #4082 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Discord username (optional)
No response
Describe the bug
I use the prompt starting at the top of the screen so my expectation on clearing screen should be that the prompt should end up at the top. Generally works but found this issue when I am using psql console.
When I open a psql console and then use clear(ctrl + L), half the screen is not utilised and is just blank. The psql prompt starts from half the screen. I have to force the console to print somethign that occupies the entire screen which then fixes it.
To reproduce
To fix:
\dt
to print something that occupies the entire screen.Expected behavior
My expectation is that on clearing screen, the prompt should end up at the top. Does not work for psql prompts alone.
Screenshots
warp-psql.-2024-03-06_11.53.02.mp4
Operating system
Linux
Operating system and version
Fedora release 37 (Thirty Seven) x86_64
Shell Version
GNU bash, version 5.2.21(1)-release (x86_64-redhat-linux-gnu)
Current Warp version
v0.2024.03.05.08.02.stable_00
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
Always been like this.
Additional context
Does this block you from using Warp daily?
No
Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)
Yes, this I confirmed this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None
The text was updated successfully, but these errors were encountered: