new-build doesn't respect `verbose:` setting in `~/.cabal/config`

[phadej]

% grep verbose ~/.cabal/config 
verbose: verbose +nowrap

% cabal new-build
Build profile: -w ghc-8.4.4 -O1
In order, the following will be built (use -v for more details):
 - haskell-ci-0.3.20190320 (lib:haskell-ci-internal) (first run)
 - haskell-ci-0.3.20190320 (exe:haskell-ci) (first run)
Preprocessing library 'haskell-ci-internal' for haskell-ci-0.3.20190320..
Building library 'haskell-ci-internal' for haskell-ci-0.3.20190320..
[34 of 34] Compiling HaskellCI        ( src/HaskellCI.hs, /home/ogre/Documents/shared-haskell/haskell-ci/dist-newstyle/build/x86_64-linux/ghc-8.4.4/haskell-ci-0.3.20190320/l/haskell-ci-internal/build/haskell-ci-internal/HaskellCI.o )
^C

% cabal new-build -vverbose+nowrap
this build was affected by the following (project) config files:
- /home/ogre/Documents/shared-haskell/haskell-ci/cabal.project
Build profile: -w ghc-8.4.4 -O1
In order, the following will be built:
 - haskell-ci-0.3.20190320 (lib:haskell-ci-internal) (first run)
 - haskell-ci-0.3.20190320 (exe:haskell-ci) (first run)
creating /home/ogre/Documents/shared-haskell/haskell-ci/dist-newstyle/build

[phadej]

Also https://cabal.readthedocs.io/en/latest/installing-packages.html#cmdoption-setup-verbose seems to be not up to date

[fgaz]

Could this be related to #5942?

[phadej]

I tried to lookup where the various configurations blocks are appended; I didn't manage to figure out.

[hvr]

This bug/issue existed for a long time; I'm surprised there wasn't already a bug filed about this hidden in our issue tracker... :-)

[bacchanalia]

Looking into this, I'm increasingly unsure if any v2- commands respect the verbose: setting.

[bacchanalia]

The only way I see of solving this is to read the configs early to find the verbosity, but there's no good to then pass the config to commands without a large rewrite, so basically every command is going to end up reading the config twice.

Is this functionality anyone actually wants? Maybe we're better off removing it instead of fixing it?

[gbaz]

Can you sketch out the issue in a bit more detail. Maybe with some pointers to the obstacle, someone else could find a solutkon?