Vifm Q&A - Recent questions and answers in vifm.vim

Answered: Is it possible to override only specific vifmrc settings when VIFM is called using vifm.vim plugin?

Fri, 10 May 2024 16:26:18 +0000

You can set g:vifm_exec_args to something like +'set vifm-=dhistory,...' to run one or more custom commands when Vifm is called from Vim.

More extensible approach could be adding +'source $VIFM/invim.vifm' and have a separate file for plugin-specific adjustments next to your vifmrc.

Answered: Issue with vim opening vifm selection during VimEnter & BufEnter

Fri, 23 Feb 2024 23:07:30 +0000

You mean that the screen isn't restored? It sounds like this issue.

I have let g:vifm_embed_term = 1 enabled and with it nothing is even opened, Ctrl-C saves the day in this case.

I'm inclined to believe Vim doesn't handle such things well in startup. Maybe postponing processing via a timer can be a workaround as it is in some other cases.

BufEnter doesn't seem to be involved, in the last part of the screencast you're running vim . as well which defines the outcome.

Answered: command! fails when screen! exists in rc file

Sat, 30 Oct 2021 15:13:02 +0000

You need to use %n macro in the command to avoid use of terminal multiplexer for running it. Or move git-add script somewhere in the $PATH for tmux/screen, or add ~/.vifm/scripts to the $PATH.

The issue is that running a command in a new window doesn't inherit current $PATH. It can actually be set, but only for all new windows as well (at least I think this was the case last time I checked).

Answered: Is there a way to set different fileviewers depending on the folder?

Thu, 10 Dec 2020 19:23:26 +0000

See patterns section of the documentation. In your case it will look something like:

fileviewer {{/path/to/SPECIALFOLDER/*.pdf}} myfancyscript %f

fileviewer *.pdf pdftotext -nopgbrk %c -

P.S. Looks like notification email got lost, saw the question just now.

Answered: Vifm not recognized as an internal or external command in Windows

Sat, 08 Aug 2020 15:30:40 +0000

Hi.

Vim plugin doesn't include the application itself. You still need to download the application and either update your %PATH% with its location or configure the plugin similar to this:

let g:vifm = 'c:/programs/vifm/vifm.exe'

The guy from YouTube already had Vifm installed.

Answered: Got a non-zeo code from vifm: 1

Sat, 04 Apr 2020 12:43:55 +0000

What version of vifm are you using? It might be too old for the latest vifm.vim, in which case you'll need to downgrade the plugin.

Answered: Error when opening a file using vifm in vim

Wed, 09 Oct 2019 10:50:10 +0000

It could be that writing to a temporary files which are used to communicate the result of running vifm has failed. Those files are created by Vim and should exist for a while though. You can try using Vim's builtin terminal or external terminal to see maybe it depends on how vifm is run.

It would be nice to be able to reproduce it, otherwise it's hard to help especially when it doesn't happen every time.