https://wiki.vifm.info/index.php?title=Diagnosing_an_issue&feed=atom&action=historyDiagnosing an issue - Revision history2024-03-28T12:21:24ZRevision history for this page on the wikiMediaWiki 1.35.1https://wiki.vifm.info/index.php?title=Diagnosing_an_issue&diff=105&oldid=prevXaizek: Initial version of the page2014-08-12T18:11:42Z<p>Initial version of the page</p>
<p><b>New page</b></p><div>==== Tracking down cause in configuration files ====<br />
<br />
While some issues can be observed independently on configuration, other ones<br />
require some specific settings or even specific sequence of commands in<br />
[[Configuration_model|configuration files]].<br />
<br />
Suggested workflow in this case is as follows:<br />
# Try [[Configuration_model#Skipping_load_of_configuration_files|running Vifm without any configuration at all]] by using <code>--no-configs</code> switch.<br />
# If the issue persists, it's likely to happen with default settings, no need to look at that direction.<br />
# Otherwise, it might be helpful to bisect the cause in configuration by:<br />
## Placing <code>:finish</code> command that stops file sourcing (no parsing after line containing this command), in the middle of configuration file, middle of the first/second half, etc.<br />
## Commenting out separate commands.</div>Xaizek