Skip to content

Conversation

Abdelilah-AIT-HAMOU
Copy link

fixing issue : #1344

this fix is suppose to fix this issues :

"During terminal window resizing (both horizontal and vertical), the following issues occur with JLine's status bar implementation:

Terminal content gets cleared unexpectedly during resize operations
Previous command outputs disappear from the visible area
Screen refreshes aggressively, causing flickering or blank screens
resizing affects the statusbar sometimes
Cursor position shifts incorrectly after resize
Vertical spacing increases with each resize operation
Terminal content doesn't reflow properly to new dimensions
Previously executed commands and their outputs become inaccessible
Scrollback buffer appears to be disrupted
Users cannot scroll up to see previous command results
"

@gnodet
Copy link
Member

gnodet commented Aug 25, 2025

With this change, some things are fixed, but some other problems appear:

  • the status bar is not redrawn at the bottom
  • when the window grows, the previous status bar is not erased

@Abdelilah-AIT-HAMOU
Copy link
Author

hey @gnodet ,
Yes, I agree that my change doesn't fix the issue 100%, especially with the redrawing behavior. I can see the status bar positioning is still problematic in some scenarios.
However, I did find a solution for the window grows case! ( i will do a PR for this case exactly )

For the status bar redrawing issue at the bottom, I'm not entirely sure about the best approach. Could you please guide me or provide some suggestions on how to handle proper redrawing in this context? I'd appreciate any pointers on:

How to ensure the status bar is properly redrawn when it should be
Best practices for invalidating/refreshing that specific region

I'm happy to update the PR with these improvements once I understand the correct approach better.
Thanks for your feedback!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants