[BUG]: Neovim freezes on exit with `:q` after closing a terminal oppened with the plugin

2KAbhishek / termim.nvim

Neovim Terminal, Improved 🦾💻

GNU General Public License v3.0

54 stars 1 forks source link

[BUG]: Neovim freezes on exit with `:q` after closing a terminal oppened with the plugin #2

Closed IsWladi closed 4 months ago

IsWladi commented 4 months ago

Description of the bug

Hi, Thank you for your plugin, I really like it! :D When using the integrated terminal feature in Neovim through the plugin termim.nvim, I encounter inconsistent behavior upon exiting Neovim. Specifically, after exiting the integrated terminal with :q and then I tried to exit Neovim with :q, Neovim freezes, requiring me to close my entire terminal session to fully exit.

Steps To Reproduce

Open Neovim.
Start a terminal with :Fterm or :Vterm (I have not tested whether this occurs with other commands of the plugin).
Close the oppened terminal using the command :q.
Try to exit Neovim with :q. Neovim is now unresponsive.

Additional Information

Using :q! to close the oppened terminal allows for normal exit from Neovim with :q. However, the freeze occurs when a terminal is opened with the plugin and closed with :q instead :q!.

IsWladi commented 4 months ago

Environment

Neovim Version: 0.9.5
termim.nvim Version: commit 87ad33c64d1a67e364191188f80f226ace98f264
Operating System: WSL2
Terminal Used: zsh

2KAbhishek commented 4 months ago

Hi @IsWladi thanks a lot for reporting this, I tried recreating the issue but I did not encounter the same issue.

This could be a WSL thing but I'm not sure yet, can you share a recording of how it looks like on your system

IsWladi commented 4 months ago

Thank you for getting back to me. The bug I reported is no longer occurring; I haven't made any changes, so it's unclear why it resolved itself, but everything seems to be working fine now. I will close the issue since the problem has ceased. Thank you for your assistance

jacoatvatfree commented 3 months ago

I'm experiencing the same issue, also when the buffer is hidden with :hide while still running. Another issue would be how to show the buffer again after hiding it.

The way I debug is to start the node project in the terminal and then to attach DAP to it, now I have the split terminal visible in the main area. I don't want to end the running node app, but I do want to hide the buffer and show it again after detaching.

2KAbhishek commented 3 months ago

@jacoatvatfree I haven't looked into hiding and unhiding terminal buffers, but it looks like something useful.

Do you want to take it up and open up a PR? I'll be available to support

Thanks