Conversation
|
You said in #13810 (reply in thread)
IMO we shouldn't do it that way, it's too unexpected and not practical that users will either remember or modify scripts which they may not control to adjust. A verbosity level could be taken from curlrc and then from the command line and go with whichever is greater. edit: Also it occurs to me multiple --config can be used so I think it should be per file, in other words verbose once in each of two config files should not equal verbosity level 2 |
|
I think this is an interesting take. I'm thinking maybe we could limit the unexpected side-effects if we make sure to only treat consecutive ones that are adjacent to each other for "leveling", and not ones that are separated by anything. So |
|
Nice idea. I like it. |
|
Implemented that a single |
- make mentioning `-v` on the curl command line increase the verbosity of the trace output - related discussion curl#13810 - make a single -v revert all previous -v+ changes - make --no-verbose also reset all trace configs
-vvon the curl command line increase the verbosity of the trace outputnetwork,protocol,proxy. Usable in--trace-config.Extract from curl's manpage on
--verbose:...
Since curl 8.10, mentioning this option several times in the same argument
increases the level of the trace output. However, as before,
a single
-v,--verboseor--no-verbosereverts any additions byprevious
-vvagain. This means that-vv -vis equivalent to-v. Thisavoids unwanted verbosity when the option is mentioned in the command line
and curl config files.
Using it twice, e.g.
-vv, will output time (--trace-time) and transferids (
--trace-ids), as well as enable tracing for all protocols(
--trace-config protocol).Adding a third verbose will output transfer content (
--trace-ascii %) andenable tracing of more components (
--trace-config read,write,ssl).A forth time will add tracing of all network components
(
--trace-config network)....