From e08b473d0eeb467ad358ba5314157753b4f37c18 Mon Sep 17 00:00:00 2001
From: cbdev <cb@cbcdn.com>
Date: Sun, 5 Jan 2020 23:26:04 +0100
Subject: Implement commandline config override (Fixes #26)

---
 README.md | 7 +++++++
 1 file changed, 7 insertions(+)

(limited to 'README.md')

diff --git a/README.md b/README.md
index e955d53..2496dfa 100644
--- a/README.md
+++ b/README.md
@@ -48,6 +48,8 @@ The MIDImonster takes as it's first argument the name of an optional configurati
 to use (`monster.cfg` is used as default if none is specified). The configuration
 file syntax is explained in the next section.
 
+The current MIDIMonster version can be queried by passing *-v* as command-line argument.
+
 ## Configuration
 
 Each protocol supported by MIDIMonster is implemented by a *backend*, which takes
@@ -76,6 +78,11 @@ To make an instance available for mapping channels, it requires at least the
 `[<backend-name> <instance-name>]` configuration stanza. Most backends require
 additional configuration for their instances.
 
+Backend and instance configuration options can also be overriden via command line
+arguments using the syntax `-b <backend>.<option>=<value>` for backend options
+and `-i <instance>.<option>=<value>` for instance options. These overrides
+are applied when the backend/instance is first mentioned in the configuration file.
+
 ### Channel mapping
 
 The `[map]` section consists of lines of channel-to-channel assignments, reading like
-- 
cgit v1.2.3