disabling "configuration override" messages appears to be impossible

I'm running taskwarrior 2.6.2 from some scripts in the form of a pipe as:

xargs -x task rc._forcecolor=1 rc.detection=0 rc.defaultwidth=$COLUMNS rc.defaultheight=$LINES (...etc...)

(the pipe / lack of terminal breaks detection, so I have to manually pass through everything) which results in a looooong list of

```
Configuration override rc._forcecolor:1
Configuration override rc.detection:0
Configuration override rc.defaultwidth:120
Configuration override rc.defaultheight:40
(...etc...)
```

that eats **way** too much of the available space and that I don't want. I'm trying to figure out what `rc.verbose` should be to get status messages etc. _but not those override lines._ From my experiments so far, it appears to be impossible.

Obviously, `rc.verbose=nothing` kills those lines. But even just trying to get `task modify` to report the number of modified task by `rc.verbose=nothing,affected` or `rc.verbose=affected` will already reintroduce the "configuration override" lines. Same goes for completely unrelated `rc.verbose=nothing,new-id` or `rc.verbose=new-id` and lots of others.

Further, it appears that those lines go to stderr instead of stdout, _which sometimes causes them to appear in the middle of the other output._ Since I don't want to get rid of _all_ error messages either / I _do_ want to get information on serious errors, redirecting `stderr` to `dev/null` is also not an acceptable solution. (It also wouldn't fix the height / required lines calculations and still waste space.)


I tried to read the code to understand what happens, but I can't follow at all.

How do I get rid of those lines?