Welcome to Vifm Q&A, where you can ask questions about Vifm usage. Registration is optional, anonymous posts are moderated. GitHub or Google logins are enabled.

Why does Vifm write $VIFM/colors/Default.vifm ?

0 votes
asked Nov 22, 2015 in vifm by aleksejrs

If I delete Vifm's configuration directory in my $HOME/.config, it always creates it with colors/Default.vifm (2333 bytes, bigger than any of the files in etc/vifm/colors/), even if I start it with --no-configs (the directory exists when Vifm is open). Why?

1 Answer

0 votes
answered Nov 22, 2015 by xaizek

Absence of colors/ directory considered to be uninitialized state of that part of configuration. If colors/ directory already exists, then Default.vifm is not created. This is a dump from internal structure with some instructions on how to edit it.

commented Nov 26, 2015 by aleksejrs

Hm, maybe it was 0.7.8 and it did not create anything else (particularly vifmrc), which confused me. 0.8 creates colors/Default.vifm, vifmrc and vifm-help.txt. Thanks (though it didn't really make sense to me with only colors/Default.vifm created).

commented Nov 26, 2015 by aleksejrs

“considered” is a past participle (причастие, не глагол) there, so it needs a “to be” (“is”) to work properly. https://en.wiktionary.org/wiki/participle#Usage_notes

Also, I think, “colors/ directory” requires a “the” or an “a” before it. Maybe “internal structure” needs it, too.

commented Nov 26, 2015 by xaizek

Yeah, I skipped "is" before "considered", which is not so uncommon in informal contexts, I guess (although not correct). As for articles, I just admit that I'm quite bad at using them as they appear to be superfluous to me and there are actual situations when you don't need them due to adjectives, but I'm not sure when exactly :-)

If you would like to make a bug report or feature request consider using GitHub, SourceForge or e-mail. Posting such things here is acceptable, but this is not a perfect place for them.