From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric S Fraga Subject: [bug] #+constants line has to be at column 0 Date: Tue, 11 Mar 2014 11:17:46 +0000 Message-ID: <874n35m1b9.fsf@pinto.chemeng.ucl.ac.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60892) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WNKhA-0005f0-CT for emacs-orgmode@gnu.org; Tue, 11 Mar 2014 07:18:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WNKh3-0006Nc-Qi for emacs-orgmode@gnu.org; Tue, 11 Mar 2014 07:18:04 -0400 Received: from mail-db3lp0079.outbound.protection.outlook.com ([213.199.154.79]:16010 helo=emea01-db3-obe.outbound.protection.outlook.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WNKh3-0006K5-Gk for emacs-orgmode@gnu.org; Tue, 11 Mar 2014 07:17:57 -0400 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: emacs-orgmode@gnu.org --=-=-= Content-Type: text/plain Hello, Unlike some other #+ directives, the #+constants: one has to be at column 0 or else it is not understood/parsed by org. This has consequences for lists. See attached example. --=-=-= Content-Type: text/x-org Content-Disposition: inline; filename="examplebug.org" #+TITLE: examplebug.org #+AUTHOR: Eric S Fraga * Table constants Assume that I have a list: 1. and in this list, one of the entries is a table 2. This is the table #+constants: param=-5 | | X | Y | | ! | x | y | |---+---+----| | # | 1 | -4 | | # | 2 | -3 | | # | 3 | -2 | #+TBLFM: $3=$x+$param 1. The constants line cannot be indented as it is not understood if it is. 2. This means that the list has been interrupted. --=-=-= Content-Type: text/plain Obviously, I can move the constants line elsewhere and/or use the $ directive within the table but I thought that this was an inconsistency in the parsing of org files? Maybe not? Org up to date and verified with emacs -Q. Thanks, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 24.3.50.2, Org release_8.2.5h-687-g9d39aa --=-=-=--