Is there an accepted standard for what a verbose flag on a CLI does?
Obviously it prints more Information to the screen than would otherwise be printed. But information that reveals what the program is doing as it does it? Should it be written for developers trying to debug an issue in mind?
@schlink in traditional unix tools adding extra v’s increased the verbosity of the output, that’s probably the closest you’ll get to a standard
@capotej right -- guess I'm asking about the nature of the added output. For example, did it describe what the program was doing as it was doing it? Was it aimed at users, or more toward (potential) developers of the tool?
@schlink usually silent programs like cp and mv tell you what they're doing with -v.
Programs that already do that by default provide more details about their progress.
It's common to be able to increase verbosity with multiple -v.
Debugging could be the highest level or an extra flag.
Also think about whether that information should go to stdout or stderr, which is a pretty important design decision.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!