Diagnosing an issue

From Vifm Wiki
Revision as of 21:11, 12 August 2014 by Xaizek (talk | contribs) (Initial version of the page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Tracking down cause in configuration files[edit]

While some issues can be observed independently on configuration, other ones require some specific settings or even specific sequence of commands in configuration files.

Suggested workflow in this case is as follows:

  1. Try running Vifm without any configuration at all by using --no-configs switch.
  2. If the issue persists, it's likely to happen with default settings, no need to look at that direction.
  3. Otherwise, it might be helpful to bisect the cause in configuration by:
    1. Placing :finish 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.
    2. Commenting out separate commands.