From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: [export] org-export-with-* bugs Date: Tue, 17 Dec 2013 20:36:56 +0100 Message-ID: <87y53jclrb.fsf@gmx.us> References: <87d2kxfou8.fsf@gmail.com> <87wqj38jy3.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]:42917) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vt0Or-0000wS-RF for emacs-orgmode@gnu.org; Tue, 17 Dec 2013 14:33:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vt0Ok-0004q5-I2 for emacs-orgmode@gnu.org; Tue, 17 Dec 2013 14:33:49 -0500 Received: from plane.gmane.org ([80.91.229.3]:60430) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vt0Ok-0004pk-CJ for emacs-orgmode@gnu.org; Tue, 17 Dec 2013 14:33:42 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Vt0Oh-0003Rn-Rn for emacs-orgmode@gnu.org; Tue, 17 Dec 2013 20:33:39 +0100 Received: from g225131055.adsl.alicedsl.de ([92.225.131.55]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 17 Dec 2013 20:33:39 +0100 Received: from rasmus by g225131055.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 17 Dec 2013 20:33:39 +0100 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 Nicolas Goaziou writes: > Hello, > > Aaron Ecay writes: > >> 1) In exporting the following org buffer to latex, I get the following >> stack trace (at end of email because of length): >> >> ===== >> #+options: |:nil >> >> | foo | bar | >> ===== > > The more I look at it, the more I'm inclined to think that it's totally > useless. I don't think anyone wants tables removed from Org syntax. > > Though, occasionally some line starting with "|" can be interpreted as > a table. In this case, it's possible to use "\vert" entity anyway. > > I'm not sure it is worth fixing. I think we really should remove it, or > change its meaning, like "|:nil means that all tables are ignored in > export process" (which is probably almost as useless). The same goes for > "::nil". I personally agree with this. I can think of no cases where it's useful /and/ =·= isn't a solution /for my use-cases/. –Rasmus -- Got mashed potatoes. Ain't got no T-Bone. No T-Bone