-
Notifications
You must be signed in to change notification settings - Fork 377
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
Ctrl-z sometimes break yazi #1309
Comments
I made some fixes to the behavior of Ctrl-Z earlier in #1307, please give it a try |
I tried applying the PR locally, but I'm not really sure if this is the correct way:
Apparently, the PR was applied. If what I was made is correct, unfortunately, the problem still persists. |
What does the |
|
Hi, I made a new PR, please try #1310 |
I tried it, and the problem still persists. |
That's so weird, with fa297b3, I can't reproduce it on my Linux VM anymore, no matter how many times I try, it works fine for me. screenshot-001857.mp4Are you sure you're using that commit right? Did I miss any details to reproduce it? |
I tried again and recorded this time. yazi-pr-1310.mp4I tried with xfce4-terminal (xfce4-terminal 0.8.10 (Xfce 4.16)) and the problem occurs in it too. I known it's hard to make sure that it's fixed, because it's not always reproducible. |
Please apply these two patches separately on top of that PR and see what happens: --- yazi/yazi-fm/src/app/commands/resume.rs
+++ yazi/yazi-fm/src/app/commands/resume_new.rs
@@ -4,7 +4,6 @@
impl App {
pub(crate) fn resume(&mut self, _: Cmd) {
- self.cx.manager.active_mut().preview.reset_image();
self.term = Some(Term::start().unwrap());
// While the app resumes, it's possible that the terminal size has changed. --- yazi/yazi-fm/src/app/commands/resume.rs
+++ yazi/yazi-fm/src/app/commands/resume_new.rs
@@ -4,13 +4,12 @@
impl App {
pub(crate) fn resume(&mut self, _: Cmd) {
- self.cx.manager.active_mut().preview.reset_image();
+ self.signals.resume(None);
+
self.term = Some(Term::start().unwrap());
// While the app resumes, it's possible that the terminal size has changed.
// We need to trigger a resize, and render the UI based on the resized area.
self.resize(());
-
- self.signals.resume(None);
}
} |
I tried both separately, but it still doesn't work. |
I have no idea then. After applying that PR, the issue completely disappeared for me, and before applying that PR, I could reproduce it with the Linux + WezTerm combo (it couldn't be reproduced on non-Linux systems or without WezTerm). I'll keep it open for a while to see if anyone else encounters it and can provide more clues and help debug it. |
This issue has been open for 2 months, no other users have reported encountering it, I can't reproduce it either, so I'm going to close it since it's not doable for me and no one can help :( My best guess is that this is related to your environment, or it's already been fixed in recent versions. |
I'm going to lock this issue because it has been closed for 30 days. ⏳ |
What system are you running Yazi on?
Linux X11
What terminal are you running Yazi in?
wezterm 20240203-110809-5046fc22
yazi --debug
outputDid you try the latest nightly build to see if the problem got fixed?
Yes, and I updated the debug information above (
yazi --debug
) to the nightly that I triedDescribe the bug
When I press ctrl-z to suspend yazi and then run fg to bring it back to foreground, the window is "freeze/broken".
This sometimes occurs, but not always, so you may need a few tries to reproduce.
Expected Behavior
Yazi should be working when it's back to foreground.
To Reproduce
run
yazi
press
ctrl-z
run
fg
to bring it back to foregroundtry using
yazi
normallyConfiguration
no config
Anything else?
The text was updated successfully, but these errors were encountered: