config coverage was quite something and brought some usage questions. To aid in test harness a --load flag was introduced.

At the moment, when running, say > config --load some_file.toml --set [feature arepa] Nu will load in memory and use that configuration file and write there instead of the default config.toml for that specific pipeline call.

This means that whenever --load is used Nu will read and write to that configuration file instead and further calls to config without passing the load flag will still use the default config.toml for reading/writing configuration data.

Perhaps introducing a --merge flag could be used as well. In other shells, users share their dotfiles. Maybe if users share their configuration files we could do something like > config --load other_user_conf.toml --merge and Nu could merge the information with the default one.