Re: [PATCH] Fix info tracepoints, etc

[Stan Shebs <stan at codesourcery dot com>]

Eli Zaretskii wrote:
> > *************** it had been deleted, but remembers the i
> > *** 4135,4144 ****
> >   that you can @dfn{enable} it again later.
> >   
> >   You disable and enable breakpoints, watchpoints, and catchpoints with
> > ! the @code{enable} and @code{disable} commands, optionally specifying one
> > ! or more breakpoint numbers as arguments.  Use @code{info break} or
> > ! @code{info watch} to print a list of breakpoints, watchpoints, and
> > ! catchpoints if you do not know which numbers to use.
> >   
> >   Disabling and enabling a breakpoint that has multiple locations
> >   affects all of its locations.
> > --- 4134,4143 ----
> >   that you can @dfn{enable} it again later.
> >   
> >   You disable and enable breakpoints, watchpoints, and catchpoints with
> > ! the @code{enable} and @code{disable} commands, optionally specifying
> > ! one or more breakpoint numbers as arguments.  Use @code{info break} to
> > ! print a list of all breakpoints, watchpoints, and catchpoints if you
> > ! do not know which numbers to use.
> >     
>
> Why did you need to remove the reference to "info watch" from this
> passage?  The command is still available, and will do its job.
>
>   

In this context, the implication is that the user wants to get a list of 
all actionpoints, and it is now the case that only "info break" will 
list everything.  If we wanted to retain a mention of "info watch", 
there would be some complicated rephrasing to clarify that "info watch" 
will not show regular breakpoints etc, and since the point of the 
sentence is just to remind the user that the info command is a 
convenient way to find out the valid actionpoint numbers, simpler seemed 
better.

Stan