Benjamin Poldrack

That seems to work. Thanks much, @yarikoptic!

Another instance in context of PR #5341: https://ci.appveyor.com/project/mih/datalad/builds/37333567/job/rml0t0urlh11jbx3#L2094

@adswa : Pushed. Is that commit fine with you?

Despite approvals, not merging yet. There are failures where tests start querying interactively, which doesn't happen on master apparently. That would suggest I somehow messed with the detection. Postponing until...

I very much agree, especially with this: > Importantly, Dataset|Repo.config will then only be necessary for performance-criticial "internal" internal implementations, while all other access (read or write) can be made...

FTR: Didn't look closely yet, but it's likely `GIT_ASKPASS` (or the config `core.askpass`) that need to be set to not let Git ask interactively. Which is currently done in our...

This seems to be the same as #4676

@yarikoptic > Just to clear up: you would like to use foreach-dataset directly on a singular dataset to benefit from all the goodies of passing various {format} variables into your...

While obviously I kinda like my suggestion, we should be aware that it still breaks behavior. If a caller explicitly specified `recursive=True` but no recursion limit before, this would behave...

Should this rather be addressed by utilizing the new `configure` command, @datalad/developers ?