From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from astoria.ccjclearline.com ([64.235.106.9]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1X20WD-0006M8-Ow for barebox@lists.infradead.org; Tue, 01 Jul 2014 16:02:54 +0000 Date: Tue, 1 Jul 2014 11:58:08 -0400 (EDT) From: "Robert P. J. Day" In-Reply-To: Message-ID: References: MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: generated command references sometimes render a solid blob of text To: Holger Schurig Cc: "U-Boot Version 2 (barebox)" On Tue, 1 Jul 2014, Holger Schurig wrote: > The Kconfig help entries (the source of the generated command > reference) have been written before python-sphinx have been > selected. > > So basically we need to go over all of them and make sure that they > render correctly. From my point of view, it doesn't harm if you see > raw ReST formatting while inside "make xconfig". normally, i wouldn't be a big fan of deliberately mangling help info for the sake of how it will *eventually* be rendered but, in this case, it seems reasonable. and on that note, is it a ReST thing that renders two regular hyphens as a single, long hyphen? as far as i can tell, that is an issue only in the let.c command help. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox