From f4249563e84cd4e4101b5d4f7afbdb9d10a984af Mon Sep 17 00:00:00 2001 From: Johan Malm Date: Sun, 24 Mar 2024 21:29:32 +0000 Subject: [PATCH] [fixup] --- docs/labwc-config.5.scd | 28 +++++++++++++++------------- 1 file changed, 15 insertions(+), 13 deletions(-) diff --git a/docs/labwc-config.5.scd b/docs/labwc-config.5.scd index ef5e1352..c163bafb 100644 --- a/docs/labwc-config.5.scd +++ b/docs/labwc-config.5.scd @@ -100,20 +100,22 @@ Configuration must be wrapped in a root-element like this: decision to increase config file flexibility and keep code simple. In practical terms, this means that `c` is usually equivalent to ``. However, there are some caveats: -- In menu.xml, the attributes `id` and `label` *must* be expressed as attributes - rather than as separate child tags. -- Ordering of attributes can sometimes be singificant. For example, when setting - fonts via attributes rather than children, - - - will set a font for active window titles, while - - - - will set a font as if `place` were unspecified, because `name` and `size` will be - processed before `place`. - + 1. In menu.xml, the attributes *id*, *label* and *execute* must be + expressed as attributes rather than as separate child elements. + + 2. Ordering of attributes can sometimes be singificant. For example, + when setting fonts via attributes rather than children, + + ** + + will set a font for active window titles, while + + ** + + will set a font as if *place* were unspecified, because *name* and + *size* will be processed before *place*. + In general, it is recommended that attributes not be used to collapse more than one level of the configuration hierarchy.