When I said:
... But it is not really important how many times *I* use it per day....
what I meant was that there are more important reasons for implementing it (not for just one user - me, but for the goodness of this IDE).
To answer to your question, well, I do few excersizes per day from few different books, currently template metaprogramming... from boost and the c++ programming language - by Stroustrup. From time to time when I either make a progress with my task or switching to another excersize I'd like to adjust this variable (for different reasons - i.e. at the beginning of a project I set max limit of errors to just one - mostly only the first one is "real error" - the rest is just schizo from compiler, but at the later stage when my project is more developed I'd like to see more errors, because then most of them are real and I'd like to see all of them or as many as possible to get my head around what's going on).
Anyway, I think having something like this (but not only with this particular scenario) is very good way of making IDE user friendly. How many times I've read error (be it dialog box, or just text) telling me that in order to correct this error I have to do such and such but how to go there wasn't mentioned. I wasted so many hours (if not days) on searching something which should be accessible from the dialog/text line which reported this error.
Don't you think that this makes sense?
