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: [RFA] info break/watch/trace use get_number_or_range, take two


Eli Zaretskii wrote:
Date: Tue, 22 Feb 2011 10:31:47 -0800
From: Michael Snyder <msnyder@vmware.com>
CC: Pedro Alves <pedro@codesourcery.com>, "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>


Eli Zaretskii wrote:
From: Pedro Alves <pedro@codesourcery.com>
Date: Tue, 22 Feb 2011 09:16:51 +0000
Cc: Michael Snyder <msnyder@vmware.com>

   add_info ("breakpoints", breakpoints_info, _("\
-Status of user-settable breakpoints, or breakpoint number NUMBER.\n\
+Status of user-settable breakpoints listed, or all breakpoints if no argument.\n\
"listed" doesn't sound obviously referring to the spec
you pass as argument to the command.  "listed where?  the
command itself is printing a list." was my thought.  Is
there any other way to spell that?
How about just losing the "listed" part?  What important information
does it convey in this context?
What wording do you suggest?

How about


Status of specified breakpoints (all user-settable breakpoints if no argument).

?

It's a deal.



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