vifm / vifm.vim Goto Github PK

I have tried setting g:vifm_term to gnome-terminal -e but I keep getting the error Got non-zero code from vifm.
I think the problem is in https://github.com/vifm/vifm.vim/blob/master/plugin/vifm.vim#L128 since gnome-terminal expects to have quotes surrounding the command (I guess). I tried adding quotes, which got me half-way. Vifm opened in gnome-terminal but I immediately got the Failed to read list of files error and nothing happened when I tried to open a file.

The code I tried (which didn't work but sort-of opened vifm in gnome-terminal) is:

execute 'silent !' g:vifm_term '"' g:vifm_exec g:vifm_exec_args ldir rdir
\ pickargsstr '"'

Am I missing something? If you can get it to work by simply setting some other gnome-terminal option (instead of -e) please let me know.

Apparently the plugin doesn't support older versions of VIFM.

When I try to open VIFM version 0.7.8 in VIM through the plugin I get the following errror:
got non-zero code from vifm: 1

I do see that the "usage" page of vifm is displayed shortly so I suppose theres an issue with the command line parameters.

Obviously I could just update VIFM but I am running this instance on a web server where I can't just update the OS or install external packages.

Cheers,
Normen

Hi,

I've tried using the default vifm debian package in Ubuntu 18.04. But it doesn't include the help :-(

I then tried to use this as a standard vim module using "vim-plug" - a popular vim plugin manager that I use. (The most popular? At least accordring to e.g. slant). Vim-plug works for every other plugin I've encountered out there.

But when I add this to my .vimrc

Plug 'vifm/vifm'

it clones the plugin into the plugins dir, but :Edit<tab> doesn't doesn't show :EditVifmas the plugin documentation will have me believe. I notice that the vifm subdir of the plugins dir is a configure/make guy and hasn't been built. "configure/make/make install" later (with a custom prefix) and I can run $PREFIX/bin/vifm. :help works too.

But entering vi and :Edit<tab> still doesn't show :EditVifm.

So I know how to build vifm from source but not how to use this as a plugin...

In my vim plugins dir, I tried:

rm -rf vifm
cp -a $PREFIX/share/vifm/vim/ vifm

because there is a $PREFIX/share/vifm/vim/plugin/vifm.vim file, but when I run vi now, I get this error:

Error detected while processing /home/peter/.vim/plugged/vifm/plugin/vifm.vim:
line   50:
E117: Unknown function: vifm#globals#Init
Press ENTER or type command to continue

And so now I ask here: What is the way to use vifm with a plugin manager?

When I switch to vifm, I can see the terminal emulator -- especially the command vim - which was used to open vim -- for a split second (almost non-noticeable).

Is there a way to prevent this visual jitter? dirvish for example doesn't do this. I don't know if it is because of :terminal's behavior or something else like spawning a new program? If so I am not sure if it can be done in a better way.

Hi, I've been following several tutorials to install vifm as I'm a newbie to Vim, but when I run the :EditVifm command with and without ~, no files or errors appear, it's just a quick flash of the screen and then shows the blank file again. Am I missing a configuration somewhere? Does this have to do with setting a certain path or environment variable somewhere? I didn't see others do that in the tutorials I followed. Thanks in advance!

Before entering the command

After entering the command

On Windows 10 with Vifm 0.11 and VIM 8.2

In VIM I am opening an instance of Vifm using :Vifm and then select a file to open by pressing return. Instead of directly opening the file instead a shell opens which I have to exit using the "exit" command and then only it goes back to VIM and shows the selected file.

VIM (plain, not NeoVim or somesuch) has been installed through the official windows installer. To install vifm I created a .vifm folder in c:\Users\Normen.vifm and copied the stuff from the "data" folder inside..

..I don't have much experience with Windows and try to replicate my Mac/Linux dev setup as good as I can on a work machine here, let me know if theres any other info you need.

Cheers for this great file manager!
Normen

It normally just fails to delete, but sometimes crashes with an error message.

I recently moved to neovim. I noticed that the line numbers are being displayed besides vifm:

This does not happen in plain vim. Any idea of how to avoid displaying them besides vifm?

I don't know if it's possible in the current implementation. But as this plugin can be opened in the embedded terminal in Vim 8, can it be posible that the terminal launches in a split in the left side as if was a sidebar?

If I run vim in a shell, :Vifm works.

But if I run gvim directly (with the UI), :Vifm throws the following message:

Error detected while processing function <SNR>41_StartVifm: line 94
CreateProcess failed

Is it possible to run :Vifm from Gvim, without being in a terminal ?

I'm using vifm 0.10.1 with vim 8.1 (including patch 1-2197).

Hello,

I have trouble having both colors and arrow/home/end keys work in vifm.vim.

With the default termwintype, I have:

• incorrect colors
• support for arrow keys

When trying to get the colors to work through this issue on vim/vim, someone suggested that I use set termwintype=conpty instead, which granted me:

• correct colors
• no more support for arrow/home/end keys

Since then I tried using :term with both termwintype values, and found out that arrow/home/end keys worked.

Since :term has support for arrow/home/end keys regardless of termwintype values, but :Vifm doesn't, I figured this was the appropriate place for my issue.

Here's a screenshot:

• on the left, set termwintype= with ability to use <up>, <down>, <left>, <right>, <home> and <end> but incorrect colors
• on the right, set termwintype=conpty with correct colors but <up>, <down>, <left>, <right>, <home> and <end> don't seem to respond

I am using gvim v8.2.1127 on Windows10.

Is there a way for me to have both correct colors, and arrow/home/end keys work ?

Hi, I'm using alacritty 0.4.3 (c723247) on OSX 10.15.5 with tmux 3.1b

vifm -v gives me:

Version: 0.10.1
Git info: built out of repository
Compiled at: Aug  1 2019 13:13:13

Support of extended keys is on
Parsing of .desktop files is enabled
Without GTK+ library
Without magic library
Without X11 library
Without dynamic loading of X11 library
With file program
With -n option for cp and mv
With remote command execution

My vifm config includes the icon settings from this post: vifm-issue 164
So in a regular vifm session (right side on img) icons are rendered as expected.
However when I'm invoking vifm from inside vim icons arent rendered at all (left side on img).
Im using MesloLGS Nerd Font Mono as my terminal font.

Any ideas why this is happening or how I can debug this?
I tried this with iterm

It is a small issue. The title of the vifm terminal is very long that it will push some useful information in the status line away from the screen. Of course, it is also not eye-candy. I wonder whether it is possible to send a command like

:file vifm

so the terminal buffer will have a short yet meaningful name.

The g:vifm_embed_split option works for horizontal split, but docs unclear how to change to vertical split instead. Documentation says one can use mods and/or count to control orientation and size.

I'm expecting something like: :EditVifm V, : EditVifm v, but nothing seems to change it. I also tried VsplitVifm, still no luck. Always opening in horizontal. What are the mod keys for vertical and for changing the size?

I'm using neovim (0.5) within tmux.

Often I browse to a file before I know whether I want to open said file in a buffer, tab, split, etc. In such things like unite and ctrlp this workflow is supported. While it is not currently possible in vifm.vim, I think it would be a great addition if possible.

I'm not really sure how it would work. It looks like you're saving selected file names into vimfiles, via vifm -f, and then immediately opening them upon returning to vim, which doesn't really facilitate the kind of workflow I am proposing.

If vifm.vim launches vifm with a custom config file, I suppose it could bind some key combinations to "open in tab", "open in vsplit", etc. commands, which would execute something slightly different for each one. Or maybe the plugin itself doesn't bind anything, and it's up to the user if they wish to buy into this.

Vifm just does not start in neovim. Any thoughts?

I’ve recently learned about vim-floaterm, which can display command-line applications in floating windows inside Neovim (Vim 8.1’s rough equivalent of this feature is called popups). There’s even a wrapper for Vifm so that it can be used as a file picker, although it only supports opening files in the current buffer. I’ve filed a request to add the ability to open files in a new tab or split (which is possible in vifm.vim through :TabVifm or :SplitVifm), but it has been rejected.

I’m wondering if it would be easier to add the option to use floating window in vifm.vim instead. (Now that the recent version of the fzf plugin for (Neo)Vim uses floating windows by default, this change would be very welcome as well.)

Edit: I’ve just realised that it might have been a better idea to post this in vifm.vim’s issue tracker. I apologise for that.

When calling Vifm with a relative path and a non-existant file like so:

:EditVifm some/directory/NULL.txt

Vim spits out the error:

Got non-zero code from vifm: 1

On the other hand, when using an absolute path the behavior is much better, Vifm starts and opens the folder.

:EditVifm ~/some/directory/NULL.txt

Thanks

At the moment, if you have termguicolors enabled in vim, :VifmCs will create a colorscheme with Hex color codes instead of 256 colors.
This would make sense if vifm were to actually support truecolor, which it currently doesn't though.

EditVifm, which was working for me for consistently, is now failing consistently with "Got non-zero code from vifm: 127"

vim and vifm both latest from homebrew (see below). vifm.vim is latest (f376392). Selection of file with vifm seems to work fine.

Any suggestions to debug?

Thanks.

VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Oct 28 2016 19:35:33)

% vifm --version
Version: 0.8.2
Git info: built out of repository
Compiled at: Jul 17 2016 17:29:41

Support of extended keys is on
Parsing of .desktop files is enabled
Without GTK+ library
Without magic library
Without X11 library
Without dynamic loading of X11 library
With file program
With -n option for cp and mv
With remote command execution

The behaviour when closing vifm in nvim has changed since 491d442. If you have two windows open and open vifm in one of them the window will close if you run :q in vifm.

Is this the indented behaviour because it feels off to me?

@rbong ☝️

I'm really happy using vifm as my file selector instead of NERDTree, which is also nice, but not as powerful. There is one functionality that I miss though. I would like vifm to stay open after opening a file (with the enter key) using the vifm file selector. I'm opening the vifm file selector using :leftabove vertical 40Vifm. This means that I should also be able to switch focus between the vifm file selector and the opened file.
Is this possible to do at the current moment?

Hello!

I work on Windows with vim8.1 (including patch 1-2197) inside a Powershell terminal (through Windows Terminal) run as Administrator.

I get the error "Got non-zero code from vifm: 255" whenever I try any vifm.vim command from within vim.

I noticed some messages appearing for a split second, indicating "Specified file was not found".

I have put the folder containing vifm.exe in the global Path.

My vimrc does not have any line related to vifm.

It has the same problem if I run vim from a simple cmd.

If I run vifm from the command line, it works. Same for :!vifm from vim.

How can I call :Vifm %:h from within vim without an error ?

hi, i have problem together with the plugin indentline it shows indentline in :TabVifm

how can i disable this?

i tried:

let g:indentLine_fileTypeExclude = ['Vifm']
let g:vim_Vifm_conceal = 0

but it doesn't work..
for anyone can help, thank you.

Edit: i fix it by setting:

let g:indentLine_bufNameExclude = ["\[vifm\]*"]

this seems to only happen with kitty terminal

call plug#begin('~/.vim/plugged')
Plug 'vifm/vifm.vim'
call plug#end()
let mapleader =" "
nnoremap n :Vifm

in nvim type
:terminal
then n

Error -
Error detected while processing function 132[13]..72_HandleRunResults:
line 2:
Got non-zero code from vifm: 1
Press ENTER or type command to continue

Is there a way to get the Vifm command to open the directory of the file I am currently editing in one pane and the working directory of Vim in the other?

I think this behavior would be a good default.

Hey 👋,

Since a couple of days ago this plugin errors for me. As soon I use the :Vifm command it outputs:

:Vifm
Error detected while processing function <SNR>56_StartVifm:
line   87:
E89: vifm: edit will be killed(add ! to override)
Press ENTER or type command to continue

I have the following settings:

" Disable netrw.
let g:loaded_netrw = 1
let g:loaded_netrwPlugin = 1

" Vifm.
let g:vifm_replace_netrw = 1
let g:vifm_term = "term"

Give me a ping if I can provide any more information to help out. I'm pretty helpless without this plugin ❤️

This should have a readme for installing isn't it? I can't seem to install it properly using pathogen.

I'm using the vifm plugin for vim on several PCs - so far without any problems. However, today I installed the plugin on a new PC where a strange problem occurs. After :EditVifm vifm shows up. However, when I select a file or a folder vifm disappears and netrw is shown instead.

I've tried to set in my .vimrc:
let g:vifm_replace_netrw = 1
but that doesn' really help: sometimes vifm remains opened, sometimes netrw shows up again.

Any ideas what might be the issue?

I'm using vifm 0.10.1 and vim 8.0.

vifm.vim/plugin/vifm.vim cannot find vifmrc in those directories.

I use https://github.com/tpope/vim-vinegar vim plugin and got used to the easy I can open file browser by simply clicking -.

But even without any special plugin, it is possible starting up vifm within neovim and do so with context of currently open file (I mean: the context exists, but is not used yet).

With directories having longer file list it would be great to have the file I started vifm from open.

vifm provides an option --select (which can be even used twice).

Warning: vifm will fail to start if the file specified by --select does not exist.

Given such functionality is implemented, review of all files in a directory shall become much simpler:

• - to open vifm, see the current file open
• j to go one file further, enter to open it
• and repeat until all files are checked

(the - assumes the vim-vinegar is installed)

Whichever command I use :VsplitVifm, :SplitVifm or :Vifm I'm getting the same result none of them is opening in split mode. I've also tried the neovifm plugin with that one I menage to get it in split mode but I was not able to map it (map <leader>f :Vifm . <cr>) though if I typed that command in the command line it worked just fine and in vsplit mode.

How can I fix this?

Hi,

Windows10/Vim 8.1 including patch 1-2197 here.

I have this line in my vifmrc: fileviewer *.cs,*.csproj bat --color always --wrap never --pager never --map-syntax csproj:xml -p %c %p

It works fine when I run vifm directly from a terminal, or from within vim-inside-terminal (vim run inside a terminal):

However, it's different when run from a terminal-started-within-vim, a terminal-started-within-gvim and gvim:

Is there anything to configure to make the colors and display right?

Hey 👋,

I just tried https://github.com/mhinz/vim-startify and vifm does not work well with it. When opening vifm from the startify screen and closing vifm it errors with the following:

Error detected while processing function 17:
line    4:
E86: Buffer 1 does not exist
Press ENTER or type command to continue

If this issue is more fitting for startify then just ping me! 🙏

I am getting the following error when I installed the plugin. I installed the plugin using vim plug and I can see it is in the ~/.vim/plugin/ directory. When I start neovim I get the following error message in nvim

Impossible to find your vifm configuration directory. Launch vifm one time and try again.

Can someone help ?

Hi,

I've tried to install the plugin on vim but hit the error bellow when i use ":EditVifm" :

Got non-zero code from vifm: 1 

I tried with a fresh install to be sure but it failed too. (running under xfce4-terminal 0.6.3)

$ echo $TERM
xterm-256color

$ lsb_release -d
Description:	Ubuntu 16.04.3 LTS

$ sudo apt-get install vifm

$ vim --version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Nov 24 2016 16:44:48)
Included patches: 1-1689
Extra patches: 8.0.0056
Modified by [email protected]
Compiled by [email protected]
Huge version without GUI.  Features included (+) or not (-):
+acl             +farsi           +mouse_netterm   +tag_binary
+arabic          +file_in_path    +mouse_sgr       +tag_old_static
+autocmd         +find_in_path    -mouse_sysmouse  -tag_any_white
-balloon_eval    +float           +mouse_urxvt     -tcl
-browse          +folding         +mouse_xterm     +terminfo
++builtin_terms  -footer          +multi_byte      +termresponse
+byte_offset     +fork()          +multi_lang      +textobjects
+channel         +gettext         -mzscheme        +timers
+cindent         -hangul_input    +netbeans_intg   +title
-clientserver    +iconv           +packages        -toolbar
-clipboard       +insert_expand   +path_extra      +user_commands
+cmdline_compl   +job             -perl            +vertsplit
+cmdline_hist    +jumplist        +persistent_undo +virtualedit
+cmdline_info    +keymap          +postscript      +visual
+comments        +langmap         +printer         +visualextra
+conceal         +libcall         +profile         +viminfo
+cryptv          +linebreak       -python          +vreplace
+cscope          +lispindent      +python3         +wildignore
+cursorbind      +listcmds        +quickfix        +wildmenu
+cursorshape     +localmap        +reltime         +windows
+dialog_con      -lua             +rightleft       +writebackup
+diff            +menu            -ruby            -X11
+digraphs        +mksession       +scrollbind      -xfontset
-dnd             +modify_fname    +signs           -xim
-ebcdic          +mouse           +smartindent     -xsmp
+emacs_tags      -mouseshape      +startuptime     -xterm_clipboard
+eval            +mouse_dec       +statusline      -xterm_save
+ex_extra        +mouse_gpm       -sun_workshop    -xpm
+extra_search    -mouse_jsbterm   +syntax          
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H   -Wdate-time  -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1      
Linking: gcc   -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o vim        -lm -ltinfo -lnsl  -lselinux  -lacl -lattr -lgpm -ldl     -L/usr/lib/python3.5/config-3.5m-x86_64-linux-gnu -lpython3.5m -lpthread -ldl -lutil -lm      


$ vifm --version
Version: 0.7.8
Git commit hash: 
Compiled at: Feb  7 2016 13:44:37

Support of extended keys is on
Parsing of .desktop files is enabled
Without GTK+ library
With magic library
With X11 library
Without dynamic loading of X11 library
With file program
With -n option for cp and mv
Without remote command execution

$ cat .vimrc
" Vim-Plug start
call plug#begin()

" File/Buffer manager
Plug 'vifm/vifm.vim'


" Initialize plugin system
call plug#end()

$ tree .vim 
.vim
├── autoload
│   └── plug.vim
└── plugged
    └── vifm.vim
        ├── autoload
        │   └── vifm
        │       ├── edit.vim
        │       └── globals.vim
        ├── doc
        │   ├── app
        │   │   └── vifm-app.txt
        │   ├── plugin
        │   │   └── vifm-plugin.txt
        │   └── tags
        ├── ftdetect
        │   ├── vifm-rename.vim
        │   └── vifm.vim
        ├── ftplugin
        │   ├── mail_vifm.vim
        │   ├── vifm-cmdedit.vim
        │   ├── vifm-edit.vim
        │   ├── vifm-rename.vim
        │   └── vifm.vim
        ├── plugin
        │   └── vifm.vim
        └── syntax
            └── vifm.vim

12 directories, 15 files

$ cd .vim/plugged/vifm.vim/
$ git rev-parse HEAD
c48e06cd4bd2fe6340f9438cab93f34bb93115a7

When i execute ":EditVifm" under vim, after quit it, we see than some messages was displayed in background :

$ vim
vifm usage:

  To start in a specific directory give the directory path.

    vifm /path/to/start/dir/one
    or
    vifm /path/to/start/dir/one  /path/to/start/dir/two

  To open file using associated program pass to vifm it's path.

  To select file prepend its path with --select.

  If no path is given vifm will start in the current working directory.

  vifm --logging
    log some errors to ~/.vifm/log.

  vifm -c <command> | +<command>
    run <command> on startup.

  vifm --version | -v
    show version number and quit.

  vifm --help | -h
    show this help message and quit.

  vifm --no-configs
    don't read vifmrc and vifminfo.

any insights ?

Regards,

question:
$ touch a.txt && vim
:EditVifm
open file

"a.txt" [converted] 0L, 0C
Error detected while processing function 60_StartVifm..60_HandleRunRes
ults:
line 56:
E471: Argument required: ^I^I^Iargadd
E471: Argument required: ^I^I^Iargadd

Is there a way to hide error messages?

request:
I would appreciate it if Add a "sort by inode".

I tried to cp files/directories to another place use yy and p, or gUU command to to rename the current file/directory, it will pop a window every time saying

Background Process Error
cp (or mv): write error: Bad file descriptor
Press Return to continue

After pressing Enter key, it will execute the command of cp or mv, but window is annoying.

FYI:
vifm
Version: 0.8.1a
Git info: v0.8.1a-31-g7d52713ef236-dirty
compiled from the git source code: ./configure --prefix=/usr; make; make install

Ubuntu 14.04 32-bit
and
CentOS 6.5 32-bit

Hello,

Currently I am able to press s from within vifm.vim and have access to a shell.

Is there a way to open vim's :terminal instead?

I guess it's due to the directory structure under doc/. I expect something like :help vifm to work.

Hi.

After installing vifm.vim, the behavior of bulkrenaming changed, irrespective of whether I am running vifm within vim: it creates a vertical split with two vim windows containing the names of the selected files.

I wonder if that is the expected behavior and if I can disable the vertical split (my display is rather small, and, so, it makes a real difference to have just one window).

Thanks a lot in advance!

I have the following mapping in my vifmrc:

nnoremap <c-\> :exit<cr>

The problem I'm facing is that I need to press <c-\> followed by any other key so that the command gets triggered. Any idea how to fix this? I noticed that this also happens with

nnoremap <c-b> :exit<cr>

but it doesn't happen with
nnoremap <c-j> :exit<cr>

I'm using tmux:

❯ tmux -Version
tmux 2.6

and this version of vifm:

❯ vifm --version
Version: 0.9.1
Git info: built out of repository

Support of extended keys is on
Parsing of .desktop files is enabled
Without GTK+ library
With magic library
With X11 library
With dynamic loading of X11 library
With file program
With -n option for cp and mv
With remote command execution

Here is a comparison of two similar workflows, first without Vifm, and then with.

bash$  ls > foo.txt
bash$ vim
:edit foo.txt

At this point, foo.txt is the only buffer in vim, having reused the buffer number of the default empty buffer.

bash$  ls > foo.txt
bash$ vim
:EditVifm
<select foo.txt>

Using this workflow, I end up with two buffers: the initial empty buffer and foo.txt.

I prefer the first behavior, but while using vifm as the file picker. Am I doing something wrong, is there a vim setting I need to change, or is this a bug?

Thanks,
Phil

Since vim 8 now supports asyncronous actions, I have added vim 8 support to neovim-vifm.

The neovim plugin is now very redundant. I am hoping to get your feedback on the possibility of merging in neovim-vifm into vifm.vim and deprecating neovim-vifm.

A couple things from my perspective will be nice to have in vifm.vim: live directory switching and running vifm in a :term. Bad things that I don't want to merge in: neovim-vifm is probably more platform dependent than vifm.vim since it relies on bash and cat currently for live directory switching. I would want to fix this before merging.

Let me know what you think, or if you have any alternative suggestions. Thanks!

After replacing netrw with vifm, the terminal is not cleaned properly.

Steps to run the problem:

1. Install vifm.vim
2. In an empty vimrc file, disable netrw and enable the g:vifm_replace_netrw flag
3. Run the command vim . in a terminal.
4. After the vifm opens inside the vim, :quit to exit
5. Vim will open an empty file, :quit again
6. The terminal will not be cleaned properly

System: Linux Mint 19.3
Shell: fish and bash
Terminal: alacritty and xterm
Multiplexer terminal: tmux (or none)
Vim version: 8.2.827
Vifm version: 0.10.1
Vifm plugin commit: 5b6291f (on May 26, 2020)

Below I’ll send a screenshot of the issue

I use neovim 0.3.1 and the latest version of vifm.vim is installed.

Every time, after using :EditVifm to open a file, the vifm terminal buffer is still dangling around but hidden. One can switch to it manually -- it means all resources are not properly released.

Further into the issue, I found when finish selecting file, the vifm process creates a new buffer with [Process existed 0]. Effectively, the :bdelete command inside callback.on_exit deletes the newly created information buffer, but keeps the vifm terminal buffer dangling around. Not sure whether it is a neovim 0.3.1 only issue.

I'm getting an error on a RasPi with the default versions included in Raspbian "Stretch":

To reproduce:

• :VsplitVfm
• select a file to open
• error appears but file opens

Error message:

Fehler beim Ausführen von "function <SNR>28_StartVifm[106]..<SNR>28_HandleRunResults":                                                                                            
Zeile   74:                                                                                                                                                                       
E319: Der Befehl ist in dieser Version nicht implementiert: drop /home/pi/npm-code/homebridge-platform-maxcube/package-lock.json                                                  
Betätigen Sie die EINGABETASTE oder geben Sie einen Befehl ein     

Vifm version:
0.8.2
Vim version:

VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Jun 21 2019 04:10:35)                                                                                                                
Inklusive der Korrekturen: 1-197, 322, 377-378, 550, 649, 651, 703, 706-707                                                                                                       
Extra patches: 8.1.1401, 8.1.1382, 8.1.1368, 8.1.1367, 8.1.1366, 8.1.1365, 8.1.1046, 8.1.0613, 8.1.0547, 8.1.0546, 8.1.0544, 8.1.0540, 8.1.0539, 8.1.0538, 8.1.0506, 8.1.0208, 8.1
.0206, 8.1.0205, 8.1.0189, 8.1.0177, 8.1.0067, 8.1.0066                                                                                                                           

Cheers,
Normen

Hi,

I can open vifm in vim but it fails when I want to open a file.

There is the following error :

:! vifm  "c:/tmp"  "--choose-files"
"C:\Users\crile\AppData\Local\Temp\VICE74D.tmp" "--on-choose" "echo
\""database_.tmpdatabase_.tmpVIFM_OPEN_TYPEdatabase_.tmpdatabase_.tmp\"">C:\Users\crile\AppData\Local\Temp\VIDE75D.tmp"
"+command EditVim   :let $VIFM_OPEN_TYPE='edit' | execute 'cnoremap j <cr>' |
normal gs:editj" "+command VsplitVim :let $VIFM_OPEN_TYPE='vsplit' | execute
'cnoremap j <cr>' | normal gs:editj" "+command SplitVim  :let
$VIFM_OPEN_TYPE='split' | execute 'cnoremap j <cr>' | normal gs:editj"
"+command DiffVim   :let $VIFM_OPEN_TYPE='vert diffsplit' | execute 'cnoremap j
<cr>' | normal gs:editj" "+command TabVim    :let $VIFM_OPEN_TYPE='tablast |
tab drop' | execute 'cnoremap j <cr>' | normal gs:editj"

Erreur détectée en traitant function <SNR>33_StartVifm[107]..<SNR>33_HandleRunResults :
ligne   55 :
E492: Commande inconnue: database_.tmpdatabase_.tmpVIFM_OPEN_TYPEdatabase_.tmpdatabase_.tmp database.tmp

Windows 10,
vifm-w64-se-0.11-binary,
vim 8.1.1

I'm using neovim. If I grep something, and then hit <cr> on a file in opened dialog, it opens the file in a new instance of neovim inside the terminal inside the neovim (another neovim instance in neovim) though if I hit <cr> in main vifm window it opens it in the main neovim instance as expected.

Hi, I'm tryng to run Vifm but I'm getting error.

"Plugins
Plug 'vifm/vifm'
Plug 'vifm/vifm.vim'

"Running neovim and trying to activate I got the error below.
:Vifm

Error detected while processing function 13[13]..32_HandleRunResults:
line 2:
Got non-zero code from vifm: 127
Press ENTER or type command to continue

"Vim version

:version
NVIM v0.4.4
Build type: Release
LuaJIT 2.0.5
Compilation: /usr/bin/clang -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNDEBUG -DMIN_LOG_LEVEL=3 -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototy
pes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=auto -DINCL
UDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -I/tmp/neovim-20200808-21571-gjtb7k/neovim-0.4.4/build/config
-I/tmp/neovim-20200808-21571-gjtb7k/neovim-0.4.4/src -I/usr/local/include -I/tmp/neovim-20200808-21571-gjtb7k/neovim-0.4.4/deps-build/include -I/usr/inclu
de -I/usr/local/opt/gettext/include -I/tmp/neovim-20200808-21571-gjtb7k/neovim-0.4.4/build/src/nvim/auto -I/tmp/neovim-20200808-21571-gjtb7k/neovim-0.4.4/b
uild/include
Compiled by brew@HighSierra

Features: +acl +iconv +tui
See ":help feature-compile"

system vimrc file: "$VIM/sysinit.vim"
fall-back for $VIM: "/usr/local/Cellar/neovim/0.4.4/share/nvim"

Run :checkhealth for more info