Tabs closes themselfs after resurrection #3694
-
|
So for example lets say that I have a tab with open nvim. Then I'm doing reboot and resurrecting that session, then I press Enter and nvim starts. But when I'm trying to exit from nvim it shows me only black screen not my terminal promt and I can only press ctrl-c and that tab closes. And all this right for all terminal programs that I run, not only nvim. Why is that so and how to fix it? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
That's the session resurrection feature. What happens is that the resurrection layout is tied to the nvim command session resurrection saved. Documentation: https://zellij.dev/documentation/session-resurrection |
Beta Was this translation helpful? Give feedback.
-
|
yeah, I'm totally ok with resurrection and like this feature. I just don't understand why when I'm closing nvim it's doesn't show me my terminal but closes the whole tab. Is it how it should be or not? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, this is by design - the session Resurrection saved that pane with the The default behavior for a non-shell application that runs in a zellij pane is to wait and restart the command if any key is hit. |
Beta Was this translation helpful? Give feedback.
-
|
omg, now I understand that I can just press |
Beta Was this translation helpful? Give feedback.
-
|
I mentioned it earlier, but it probably slipped your attention: |
Beta Was this translation helpful? Give feedback.
Yes, this is by design - the session Resurrection saved that pane with the
nvim command line, not with the shell running that command line.The default behavior for a non-shell application that runs in a zellij pane is to wait and restart the command if any key is hit.
Think about a development environment where you want to test your app - it runs then exits, you want to keep the code editor on one pane and the execution on another - if upon exit, that pane closes, you can't see the output, so by default, zelilj assumes the output is important and stays suspended - waiting for any key to retry, Ctrl+c to close, or ESC to drop to the shell.