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][patch 1/9] Yet another respin of the patch with initial Python support


On Sat, 2008-07-26 at 21:10 +0300, Eli Zaretskii wrote:
> > From: Tom Tromey <tromey@redhat.com>
> > >> +@value{GDBN} exposes a number of features to Python scripts.
> > 
> > Eli> This should end with a colon, and the list of the features should be a
> > Eli> @table.
> > 
> > I guess those aren't really features, they are more like generic
> > things that the python-in-gdb programmer ought to know.
> > 
> > So, I don't think a table makes sense, but I suppose the current text
> > is also misleading.  What do you suggest?
> 
> My problem is with the form, not with the content.  By default, each
> paragraph in a Texinfo document starts with an indentation, like in a
> book.  @table prevents that, producing paragraphs whose all lines line
> up.  This section presents a list of features; having each feature's
> description begin with an indented line is simply ugly.

We can sidestep the issue and actually get a better result in the end:

The two paragraphs talking about exception handling should go to a new
subsubsection, and the paragraph stdout and pagination should go to the
"Basic Python" subsubsection.

Then we can whack the "GDB exposes a number of features to Python
scripts." sentence.

IMO it is the best option.

> You seem to think that @table produces a table, but it doesn't.

Heh. :-)
-- 
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center


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