xaizek
Hi, If I set `termwintype=conpty` on Windows10 on Vim from [here](https://github.com/vim/vim-win32-installer/releases), I get "ConPTY isn't supported" message and can't test this. I think embedding shouldn't matter for terminal applications. If...
Looks like neovim (but not Vim) doesn't allow multiple terminal buffers with identical name, you get the message when you try to open second Vifm buffer. Buffer name matters only...
> I’m wondering if it would be easier to add the option to use floating window in vifm.vim instead. Haven't looked much at the relevant API, so it's hard to...
> On the other hand, when using an absolute path the behavior is much better, Vifm starts and opens the folder. Actually, this part looks like a bug. Both kinds...
> The docs says that file or files is part of the argument. Should it not mention directories as well? That's description of a command, not its arguments. Arguments are...
If you point `g:vifm_exec` to the script: ```vim let g:vifm_exec = expand('$HOME/.config/vifm/vifmrun') ``` It will work, however it won't account for Vim's window offset.
You shouldn't need quotes if you use `-x` option, which takes the rest of command-line as a command (according to [this](http://manpages.ubuntu.com/manpages/hardy/man1/gnome-terminal.1.html)). The second issue you faced is that terminal detaches/forks...
With `vifm.vim` being the only plugin in Vim 8.2.801 with such `~/.vimrc`: ```vim let g:loaded_netrw = 1 let g:loaded_netrwPlugin = 1 let g:vifm_replace_netrw = 1 ``` I don't see any...
I misunderstood you initially, I see it now. Thanks. Maybe something can be done about it if it's not an artifact of running external applications inside Vim's autocommand.
Transferred the issue.