From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: tabularx from org to latex not recognized Date: Tue, 03 May 2016 16:35:36 -0400 Message-ID: <87twienalj.fsf@gmail.com> References: <353cd935a9364ccc82fa15105e65d4a5@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> <871t5j2n9a.fsf@ucl.ac.uk> <877ffbdty5.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46671) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1axh3K-0007EJ-Hf for emacs-orgmode@gnu.org; Tue, 03 May 2016 16:36:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1axh2z-000327-GS for emacs-orgmode@gnu.org; Tue, 03 May 2016 16:36:13 -0400 Received: from plane.gmane.org ([80.91.229.3]:33739) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1axh2z-0002xy-9Z for emacs-orgmode@gnu.org; Tue, 03 May 2016 16:35:57 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1axh2o-0003mY-Ff for emacs-orgmode@gnu.org; Tue, 03 May 2016 22:35:46 +0200 Received: from nat-pool-bos-t.redhat.com ([66.187.233.206]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 May 2016 22:35:46 +0200 Received: from ndokos by nat-pool-bos-t.redhat.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 May 2016 22:35:46 +0200 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" To: emacs-orgmode@gnu.org Nick Dokos writes: > The OP should try moving the #+ATTR_LATEX line to just before the table. > I'm not sure, but I don't think it applies long distance. > I checked, so now I'm sure :-) - see the org-syntax document on Worg, section "Affiliated Keywords" (http://orgmode.org/worg/dev/org-syntax.html#Affiliated_keywords): ,---- | Affiliated Keywords | | With the exception of inlinetasks, items, planning, clocks, node | properties and table rows, every other element type can be assigned | attributes. | | This is done by adding specific keywords, named “affiliated keywords”, | just above the element considered, no blank line allowed. | | Affiliated keywords are built upon one of the following patterns: | “#+KEY: VALUE”, “#+KEY[OPTIONAL]: VALUE” or “#+ATTR_BACKEND: VALUE”. | | ... `---- -- Nick