From 6c9d18b66c94c6ac14c8529690b3b0c700fe05f5 Mon Sep 17 00:00:00 2001
From: Boris Kolpackov <boris@codesynthesis.com>
Date: Wed, 23 Mar 2022 09:28:48 +0200
Subject: Document config.config.disfigure

---
 doc/manual.cli | 20 +++++++++++++++++++-
 1 file changed, 19 insertions(+), 1 deletion(-)

(limited to 'doc/manual.cli')

diff --git a/doc/manual.cli b/doc/manual.cli
index fcee403..910ca0a 100644
--- a/doc/manual.cli
+++ b/doc/manual.cli
@@ -1705,9 +1705,18 @@ $ b
 ...
 \
 
-Let's take a look at \c{config.build}:
+To remove the persistent configuration we use the \c{disfigure}
+meta-operation:
 
 \
+$ b disfigure
+\
+
+Let's again configure our project and take a look at \c{config.build}:
+
+\
+$ b configure config.cxx=clang++ config.cxx.coptions=-g
+
 $ cat build/config.build
 
 config.cxx = clang++
@@ -1742,6 +1751,15 @@ Any variable value specified on the command line overrides those specified in
 the \c{buildfiles}. As a result, \c{config.cxx} was updated while the value of
 \c{config.cxx.coptions} was preserved.
 
+\N|To revert a configuration variable to its default value, list its name in
+the special \c{config.config.disfigure} variable. For example:
+
+\
+$ b configure config.config.disfigure=config.cxx
+\
+
+|
+
 Command line variable overrides are also handy to adjust the configuration for
 a single build system invocation. For example, let's say we want to quickly
 check that our project builds with optimization but without permanently
-- 
cgit v1.1