search

daa84 / neovim-gtk

gtk ui for neovim
GNU General Public License v3.0
718 stars 56 forks source link

Use nvim.command_async where possible #71

Closed christopher-l closed 6 years ago

christopher-l commented 6 years ago

Pretty much what the title says.

The reason for my original problem turned out to be the call to nvim.eval() from connect_row_activated(), but I guess this doesn't hurt.

The problem I observed was a hang-up when calling :ls and then clicking an entry of the file tree without closing the output by hitting return first.

daa84 commented 6 years ago

Yes, this is problem. Some time ago i try to solve it by use https://github.com/daa84/neovim-gtk/blob/6ed33aa786fe10367831acbf045c13cdd78dbb89/src/shell.rs#L131 This call can be used to determine that neovim is blocked due to user input. But funny thing is that this call also can in some cases be blocked.