Spec: Use fences for code blocks
@@ -55,8 +55,10 @@ Actions can also be specified on a per conflict basis. Those actions take preced
Examples:
+```
conflict/get/member = WARNING
conflict/set/range = ERROR
+```
### Per Key Configuration
@@ -64,24 +66,29 @@ Actions can also be specified per-key. Those will take precedence over basic and
Example:
+```
spec/test/#
conflict/get/member = INFO
+```
## Examples
Ini files can be found in [/examples/spec](/examples/spec) which should be PWD
so that the example works:
+```sh
cd ~e/examples/spec
kdb global-mount # mounts spec plugin by default
kdb mount $PWD/spec.ini spec ni
kdb mount $PWD/spectest.ini /testkey ni
kdb export /testkey ni # note: spec can only applied on cascading access
+```
With spec mount one can use (in this case battery.ini needs to be installed in
`kdb file spec` (this should be preferred on non-development machines so that
everything still works after the source is removed):
+```sh
cp battery.ini $(dirname $(kdb file spec))
kdb mount battery.ini spec/example/battery ni
kdb spec-mount /example/battery
@@ -98,4 +105,5 @@ everything still works after the source is removed):
kdb export spec/freedesktop/openicc ni # give us details about the specification
kdb lsmeta /freedesktop/openicc/device/camera/#0/EXIF_serial # seems like there is a check/type
kdb set "/freedesktop/openicc/device/camera/#0/EXIF_serial" 203 # success, is a long
- kdb set "set "/freedesktop/openicc/device/camera/#0/EXIF_serial" x # fails, not a long
+kdb set "/freedesktop/openicc/device/camera/#0/EXIF_serial" x # fails, not a long
+```
