-
Notifications
You must be signed in to change notification settings - Fork 815
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
fix(app): fix inline_no_clear
#5022
fix(app): fix inline_no_clear
#5022
Conversation
@@ -2909,10 +2909,14 @@ async def invoke_ready_callback() -> None: | |||
self._driver.write( | |||
Control.move(-cursor_x, -cursor_y + 1).segment.text | |||
) | |||
if inline_no_clear and not not self.app._exit_renderables: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The "not not" is a bug. I think the reasoning was that if there are errors (in the exit renderables) they should be printed rather than the last frame.
@TomJGooding Sorry for usurping your PR. This seems to give the results we are looking for (from experimentation) |
No problem. I did notice now running the example in issue #4882 leaves a bit of a gap before the start of the error message, but probably not really an issue.. |
Fixes #5019.
I'm afraid I don't fully understand commit 8c01ef7, but this change seems to fix the broken
inline_no_clear
without any regression related to issue #4882 which I believe this commit intended to fix.