Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vifm.vim remains opened in a hidden buffer after running vim <DIR> and picking a file #95

Open
intelfx opened this issue Jun 22, 2024 · 2 comments
Labels

Comments

@intelfx
Copy link

intelfx commented Jun 22, 2024

Description

There seems to be a usability issue with vifm.vim w/embedding + netrw replacement.

When vim is started as vim <DIR> directly into a vifm.vim buffer, after picking a file vifm.vim does not terminate and remains in a hidden buffer. Thus, when I edit the file and attempt to exit Vim via :q, I get an error:

E947: Job still running in buffer "vifm: edit"

If I then pick another file, the embedded instance does terminate. ISTM that it should do so in the beginning as well.

Environment

intelfx added a commit to intelfx/dotfiles that referenced this issue Jun 23, 2024
@xaizek xaizek added the bug label Jun 28, 2024
@xaizek
Copy link
Member

xaizek commented Jun 28, 2024

Thanks for the report. There is clearly an issue. Vifm does terminate after picking a file, otherwise nothing would get opened in Vim, but Vifm is started again in a new buffer right after that.

@intelfx
Copy link
Author

intelfx commented Jun 28, 2024

Vifm does terminate after picking a file, otherwise nothing would get opened in Vim, but Vifm is started again in a new buffer right after that.

Ah, right. I described the user-visible effects :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants