Klemens Böswirth

"Null key" is an established term yes. But this actually a reason to **not** call the function `keyNull()`. The point is not creating a key without a value. The point...

Where exactly do you see the contradiction? "I just want an instance of Key. I don't care what it contains." implies a call to `keyNew` since that is the only...

> an empty Key should look something like `keyNew("", KEY_END)` That doesn't work since #3555, because `""` is not a valid (escaped) key name anymore. > are there any situations...

@markus2330 is a change like this still in discussion? For some versions automatic refactoring may be possible. Also, with the new idea of a `libelektra-operations` library, the best variant for...

Just passing the name (and separately the namespace) was my idea at first too, since every `Key` must have a name. However, this means one of three things needs to...

How would that work? The best solution I can think of is something like this: ``` source $(kdb parse-opts ni specfile.ini VAR1=/some/key/one VAR2=/some/key/two -- "$@") ``` It would read `specfile.ini`...

> Often you have applications and shell scripts accessing the same configuration (specification). Okay, that make sense... I will think about doing this after to options plugin is done

> it could even be kdb get but it would need some option-escaping Not a fan of that... It is not very KISS to make `kdb get` do that >...

This should be much easier to implement, once #3651 is merged.

> As I have de-registrered from the course, I won't do any work on these tasks anymore Sorry to here that. I updated the issue description with more details and...