Neal Gompa suggested running KWin with the --locale1 flag, which
makes it listen to locale1 changes. For systems that don't support
that, there is now a different approach that rudely writes the
config file -- which you should probably then copy into the
target system later with a *preservefiles* module.
FIXES#2264
Running `kwin_wayland --locale1` makes KWin listen to locale1
for keyboard updates, but not everybody has that. Introduce a
KWin-specific configuration flag that will (re)write the
KWin configuration.
The timer can be connected to one slot, which just
checks what kinds of configuration are enabled.
Then update all the ones that make sense in a live system.
While here, adjust the format for changelog entries a little.
Use "given name" instead of "first name", since "first / middle / last"
doesn't make sense in a lot of contexts. Mention issue numbers
and names for individual entries where possible.
My development machine has Python 3.11 installed, with all the
development tools, and 3.12 with only the interpreter. I can't
get find_package(Python3) to find 3.11 unless specifying EXACT,
since it always ends up preferring 3.12 which doesn't have the
required components.
The base-URI of the schema is already set; references
that are relative and contain only a fragment (e.g. start with `#`)
resolve against the base-URI, so that's within this document.
Since we already have `definitions` as a key, `#/definitions`
references that sub-schema. We don't need the `$id` settings in
each sub-schema, which messes up the base-URI; it should have been
an `$anchor`, maybe, but isn't necessary after all.
3.3.0 wasn't a good choice and we **know** we're
not stable relative to that. Later release 3.3.3
introduced better visibility controls to reduce
the size of the interface that needs to be considered.
- Adding another example command broke the test which checks
the number of entries in the example script.
- Add a second line of output to the example command, so it makes
more sense to log it line-by-line.
