Rename: Use fences for code blocks
@@ -75,6 +75,7 @@ The cut operation takes as its only configuration parameter the key name part to
different ways. First, the global configuration key `cut` can be used. Second, keys to be stripped can be tagged with the MetaKey `rename/cut`.
If both options are given, the MetaKey takes precedence. For example, consider the following setup:
+```
config/cut = will/be
parent key = user/config
@@ -82,13 +83,16 @@ If both options are given, the MetaKey takes precedence. For example, consider t
user/config/will/be/stripped/key2 <- meta rename/cut = will/be/stripped
user/config/will/be/stripped/key3
user/config/will/not/be/stripped/key4
+```
The result of the cut operation would be the following KeySet:
+```
user/config/key1
user/config/key2
user/config/stripped/key3
user/config/will/not/be/stripped/key4
+```
The cut operation is agnostic to a single trailing slash in the configuration. This means that it makes no difference whether `cut = will/be/stripped`
or `cut = will/be/stripped/`. However, the cut operation refuses cut paths with leading slash. This is to clarify that key name parts can only be stripped
@@ -111,8 +115,10 @@ The toupper/tolower conversions are applied after cut/replace.
Note that the names refer to the representation as KeySet. For example, if you have a configuration file where every name is uppercase:
+```ini
KEY=value
OTHER/KEY=otherval
+```
you can use `tolower=0` to get the keys `key` and `other/key`.
