Leon

I suspect it is the border window that is hanging around. For neovim > 0.5 this might be solved by #343. @oblitum Could you try that PR and see if...

Relevant section of `:h neovim_open_win`: ``` • border: Style of (optional) window border. This can either be a string or an array. The string values are • "none": No border...

Of course the border chars are specified in a different order, ugh. From vim: ``` borderchars List with characters, defining the character to use for the top/right/bottom/left border. Optionally followed...

@voldikss Any thoughts on what to do about the window title in this case? ~~I've opened an issue at neovim, but it could take some time to arrive: https://github.com/neovim/neovim/issues/17458~~ The...

If you are still using vifm, maybe you would like to implement this and send a PR. I would fix this but I don't use the file manager extensions so...

I propose that this option should be removed completely. Startinsert can be controlled by the users with autocommands, there is no need for us to have this.

Please provide some more info, like are you on neovim/vim, what is `g:floaterm_wintype` etc.

@jayschwa > it now works because of XWayland Are there any plans for supporting Wayland-only compositors? I'm not too knowledgable about all this (so I don't know how much effort...

Since last month I've had to get XWayland running for other stuff anyway, and unfortunately I don't see myself putting much work into this very soon. Here are a few...

Some things I have tried on the Arch machine: - deleting cache, e.g. `.pytest_cache`, `.mypy_cache`, `tests/__pycache__` - deleting and recreating the `venv` environments Nothing changes, I'll now try to add...