dannyneira
commented
1 year ago Hi @maciej-gromul How clear works in Warp currently is by pushing the content out of the view, so it could be the previous clear block is somehow getting called in the kubectx command somehow. I was able to reproduce this issue with just running kubectx after clear. We'll post any updates on this thread.
Discord username (optional)
No response
Describe the bug
When using kubectx to verify context terminal shows for a second clear command executed earlier. Then it vanishes making everything jump for a second. Clear doesn't seem to remove blocks but adds enough lines to make previous responses vanish.
To Reproduce
Called few commands to have some output blocks. Then called clear to clear blocks in terminal. With "empty" warp terminal called kubectx to verify kube context i'm on.
The moment kubectx started executing it happened. On top I could see the clear command block for around a second, after that it vanishes and on bottom i get kubectx result block.
Expected behaviour
Not having that "jump" behaviour showing presumably removed blocks from the terminal. I guess clear could be detected and remove blocks from memory ? Or make that as option to do so configurable in the app.
Screenshots
Operating System
None
OS Version
13.1 (22C65)
Shell Version
zsh 5.8 (x86_64-apple-darwin20.1.0)
Warp Version
v0.2023.02.28.08.03.stable_01
Additional context
No response
Does this block you from using Warp daily?
No
Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e
None