xaizek

Are you talking about previewing graphics? Text preview is asynchronous, graphical preview isn't because there needs to be a particular ordering to draw and clear operations for the output to...

Right, builtin preview is also synchronous, mostly because I didn't expect any slowliness there. You can work around it by viewing directories using an external application, e.g.: ```vim fileviewer .*/,*/...

`[...]` indicates that previewer is in fact asynchronous. Previewing does need to query current file for changes, but not sure that can be the cause behind such significant slowdown. I...

> What I have seen is that with the current behaviour a new file with the same name is created with respect to the project folder by my editor instance...

That `editor` directory is [a plugin](https://wiki.vifm.info/index.php/Using_Lua_plugins#Overview), you can save it locally as `$VIFM/plugins/editor/` and modify `vim.lua` to your liking (or copy, rename it and add a line to `init.lua`), then...

That's the expected behaviour, `:tree` in a custom view constructs a tree out of the list of files of the custom view.

That would need a parameter for `:tree`. Currently, custom nature of file list takes precedence. Is your use case a one-time directory expansion (like `find` does) or you expected to...

> I have to use `:exe 'sp' expand('%c')` instead. `sp | cd . %c` seems easier. > By the way, like in Vim, `:sp` should also activate the pane (no...

> I was wondering if it's possible for only `[present]` programs to be shown in `:file` menu? Nope, as of now the menu always contains all registered commands.

You are mixing custom views and menus, although maybe you're using a menu because views can only contain paths that exist. Either way, `vifm.menus.loadcustom()` merely loads the menu, but it...