From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: latex exporting strangeness [was: Re: Tables and Latex "Wrong-number-of-arguments" error] Date: Mon, 09 Mar 2009 18:42:51 -0400 Message-ID: <11211.1236638571@alphaville.usa.hp.com> References: <8aca08a00903041048g7318ec54v904b984a50daf4c7@mail.gmail.com> <30B609E1-98D5-4A78-9A20-FCB803263DC7@uva.nl> <8aca08a00903091315r12623c88r3c50f2ef6c7aa8bf@mail.gmail.com> <11073.1236637352@alphaville.usa.hp.com> Reply-To: nicholas.dokos@hp.com Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LgoCI-0003FZ-7Z for emacs-orgmode@gnu.org; Mon, 09 Mar 2009 18:43:46 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LgoCF-0003Am-7T for emacs-orgmode@gnu.org; Mon, 09 Mar 2009 18:43:45 -0400 Received: from [199.232.76.173] (port=49296 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LgoCE-0003AA-Hr for emacs-orgmode@gnu.org; Mon, 09 Mar 2009 18:43:42 -0400 Received: from g1t0029.austin.hp.com ([15.216.28.36]:19859) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LgoCD-0005Pc-V6 for emacs-orgmode@gnu.org; Mon, 09 Mar 2009 18:43:42 -0400 In-Reply-To: Message from Nick Dokos of "Mon, 09 Mar 2009 18:22:32 EDT." <11073.1236637352@alphaville.usa.hp.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: nicholas.dokos@hp.com Cc: andrew dasys , emacs-orgmode@gnu.org [replying to my own mail] Nick Dokos wrote: > > I said above that the export succeeds and it does, in the sense that I > get no errors. However, the exported latex looks strange - the table > comes *before* the "MASH" section. Is this a bug or is it a peculiarity > of my configuration? Can somebody please try it and let me know? > I seem to recall that this has come up before: basically, an empty line at the beginning of the org file restores sanity. So even if it is a bug, there is an easy workaround. Sorry for the noise, Nick