https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85664
--- Comment #4 from Mysha <gcc at mailed dot e4ward.com> --- > The suggestions are eminently useful... Which is why I said I would prefer to have a --terse option. After all, having such an option implies that you can choose not to use them. > If you don't like getting too many errors or verbose output, you can use > -fmax-errors=1 -fno-diagnostics-show-caret -fno-diagnostics-show-option. ... Great. It turns out the impression I got from the reactions to the two reports, that there was no option to be terse, was mistaken. My trust in GCC is restored. Thank you. (You know why I didn't know.) > ... we have also bug reports asking for messages to be more verbose. ..." It's OK to feel attacked. It's the same I feel for getting a reply about something I didn't say, on a topic that wasn't even the focus of the report. I wrote I would have "--terse" (or words to that effect), and only because I understood that these informative extras were the only way, currently. I did not write "I want GCC to be different for everybody because something the developers considered a good thing doesn't always suit my particular situation." Right, we've now both defended ourselves. Let's continue on what I did write. (And if you happen to be part of the European Youth Music Festival, let me know where you are and we'll have a drink together.) > Removing the questions do not save lines. Indeed, which is why these two reports are related, but not duplicates.
