Klemens Böswirth

For the `passwd` resolution, we should use `SUDO_UID`. For the `HOME`, `XDG_CONFIG_HOME` and built-in fallback I don't see a good solution when using `sudo`. Also when you do ``` sudo...

I think we are seriously over-complicating things here. AFAIK root can currently already access `user:/` keys of other users. This works by simply using `sudo -u`: ```sh sudo -u otheruser...

> Unfortunately, this does not seem to work under WSL. Curiously, the environment variable `LOGNAME` is defined, but running the command `logname` yields the error "logname: no login name". Seems...

> In general environment variables are [...] we want to avoid that applications executed from different shells, started by different desktop environments etc. have different configurations. I fully agree. But...

> I don't exclude the possibility that the log should be outside of KDB. Not responding at all to my suggestion -- which I think was a valid suggestion, since...

@atmaxinger: I fully agree that you need to decide what we do in regards to `kdb record`. There are now enough suggestions that you should be able to find a...

IMO `ksSearch` should not handle the lookup of cascading keys automatically. This would confuse the two separate functionalities. To me `ksSearch` checks whether or not a _specific key_ is contained...

> do the right thing (the cascading lookup) IMO that's not the right thing, because the lookup is a behaviour of `ksLookup` and not something intrinsic to a `Key` with...

> Cascading keys (i.e. keys from namespace KEY_NS_CASCADING) only purpose is to be looked up. Also see glossary. That's definitely not how they are used throughout the code base. There...

One thing I noticed when looking at #4420, cascading keys are definitely also used for defining cascading backends (as done by `spec-mount`). The use case is very similar to lookup...