xaizek

Hello, > first of all I would like to thank you and all contributors for creating this promising file manager for the fans of the vim-like-techniques. Credit for the actual...

> this brings it to some kind of collision, if files were already colored using expressions depending on their extension Not really, existing file highlighting rules affect only file name...

Something like this would be useful. It was suggested before to reduce duplication between `:filetype` and `:fileviewer`, highlighting couldn't be file specific back then. Maybe it can all be solved...

> Note that Vim does not create local configuration files at all. I suggest that Vifm make a copy with everything commented out. Yet Vim installs system-wide configuration file, while...

> Maybe my use of many user accounts is also an exception (where does the supposed security of “Linux” come from, then?). If you actively using them all the same...

> 425 lines including comments. There is a 25-line comment block for file[x]type. I agree it makes poor documentation (no mention of filetype vs filextype), but there is no warning...

Indeed interesting idea.

Have you seen [`:source`](https://vifm.info/vimdoc.shtml#vifm-%3Asource) command? I think that's what you want.

No, it can't expand globs. And the workaround is quite awful and seems to be to generate file that contains `source something` lines and source that...

Autoloading behaviour is more akin to Vim's `plugin/` directory, `autoload/` loads files on demand which isn't suitable here. Glob expansion seems to be more flexible, you can also avoid globs...