From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7983 invoked by alias); 5 Aug 2008 18:14:12 -0000 Received: (qmail 7975 invoked by uid 22791); 5 Aug 2008 18:14:12 -0000 X-Spam-Check-By: sourceware.org Received: from mtaout7.012.net.il (HELO mtaout7.012.net.il) (84.95.2.19) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 05 Aug 2008 18:13:33 +0000 Received: from HOME-C4E4A596F7 ([77.126.7.152]) by i-mtaout7.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0K5500K3R3YVIC30@i-mtaout7.012.net.il> for gdb-patches@sourceware.org; Tue, 05 Aug 2008 21:13:44 +0300 (IDT) Date: Tue, 05 Aug 2008 18:14:00 -0000 From: Eli Zaretskii Subject: Re: [RFA][patch 1/9] Yet another respin of the patch with initial Python support In-reply-to: <1217909927.7578.61.camel@localhost.localdomain> X-012-Sender: halo1@inter.net.il To: Thiago Jung Bauermann Cc: tromey@redhat.com, drow@false.org, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: References: <20080429155212.444237503@br.ibm.com> <20080429155304.288626880@br.ibm.com> <20080528205921.GA2969@caradoc.them.org> <20080615181833.uxmo25mg0kko40kw@imap.linux.ibm.com> <1216107418.14956.27.camel@localhost.localdomain> <1216245620.12209.18.camel@localhost.localdomain> <20080718195010.GA14356@caradoc.them.org> <1216653969.31797.6.camel@localhost.localdomain> <1217909927.7578.61.camel@localhost.localdomain> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-08/txt/msg00080.txt.bz2 > From: Thiago Jung Bauermann > Cc: tromey@redhat.com, drow@false.org, gdb-patches@sourceware.org > Date: Tue, 05 Aug 2008 01:18:47 -0300 > > > 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. Can you show me the patch along those lines?