From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Bug: manual for table column width and alignment [7.9.3a (7.9.3a-elpa @ /home/joost/.emacs.d/elpa/org-20130108/)] Date: Sat, 26 Jan 2013 11:47:59 +0100 Message-ID: <87vcak6x0g.fsf@bzg.ath.cx> References: <20130125.112444.464105277053150974.joost@snow.nl> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:60640) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tz3In-00036l-0U for emacs-orgmode@gnu.org; Sat, 26 Jan 2013 05:48:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tz3Il-0003vs-OW for emacs-orgmode@gnu.org; Sat, 26 Jan 2013 05:48:00 -0500 Received: from we-in-x022b.1e100.net ([2a00:1450:400c:c03::22b]:51377 helo=mail-we0-x22b.google.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tz3Il-0003vm-D9 for emacs-orgmode@gnu.org; Sat, 26 Jan 2013 05:47:59 -0500 Received: by mail-we0-f171.google.com with SMTP id u54so610141wey.30 for ; Sat, 26 Jan 2013 02:47:58 -0800 (PST) In-Reply-To: <20130125.112444.464105277053150974.joost@snow.nl> (Joost Helberg's message of "Fri, 25 Jan 2013 11:24:44 +0100 (CET)") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Joost Helberg Cc: emacs-orgmode@gnu.org Hi Joost, Joost Helberg writes: > The manual states that the width and alignment values can be > combined. The example uses a combination of and <10>. The `l' is > not the best way to demonstrate this, as it looks like a `1'. The > scanning reader may see <110> instead of . If the manual reads > , the example is a lot more valuable. Done. > Also, in order to not rely > on an example only, the text `may also combine alignment and field > width' will be better if it reads `may also combine alignment and > field width as a single multi letter specification within pointy > brackets' I don't find this necessary, the sentence is too heavy like this. Thanks, -- Bastien