This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [cancel] [patch] More suggestive error_is_running message


> In general GDB should always suggest possible solutions to a problem.
> Stating just the problem may not be enough for the user.

Agreed on that. I have learnt to appreciate git's helpful hints
when something happens. We just need to find the right wording
to avoid being too verbose and undoing some of the benefits of
the work done earlier to cut on verbosity.  I realize it is
a little disingenous of me to put everything on the same level,
as some of the verbose output that was removed was simply useless
or redundant, but I didn't know how to express it concisely.

Anyway, what I was also trying to say is that my comments where
meant to try to help with the wording. More often than not,
I'll settle for something that works, or is good enough, even
if it's not perfect. We both use English as a second language,
so it's normal that we're having a tougher time writing good
English error messages.

-- 
Joel


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]