From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Ecay Subject: Re: [export] org-export-with-* bugs Date: Wed, 18 Dec 2013 00:24:46 -0500 Message-ID: <87mwjyenoh.fsf@gmail.com> References: <87d2kxfou8.fsf@gmail.com> <87wqj38jy3.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34875) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vt9cv-0007bB-Gw for emacs-orgmode@gnu.org; Wed, 18 Dec 2013 00:25:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vt9cn-0000TE-2X for emacs-orgmode@gnu.org; Wed, 18 Dec 2013 00:24:57 -0500 Received: from mail-qe0-x231.google.com ([2607:f8b0:400d:c02::231]:37435) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vt9cm-0000T9-UI for emacs-orgmode@gnu.org; Wed, 18 Dec 2013 00:24:48 -0500 Received: by mail-qe0-f49.google.com with SMTP id w7so6044539qeb.36 for ; Tue, 17 Dec 2013 21:24:48 -0800 (PST) In-Reply-To: <87wqj38jy3.fsf@gmail.com> 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: Nicolas Goaziou , emacs-orgmode@gnu.org 2013ko abenudak 17an, Nicolas Goaziou-ek idatzi zuen: > 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. >=20 > Though, occasionally some line starting with "|" can be interpreted as > a table. In this case, it's possible to use "\vert" entity anyway. >=20 > 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 think either suggestion (total removal or changing semantics) is a reasonable option. > I attach a patch that should solve this (but doesn't handle tables or > fixed-width areas). (fixed-width is one of the branches in the =E2=80=98case=E2=80=99 form in t= he new code...?) I can confirm the fix. It looks like the new mechanism is equivalent to a parse tree filter. (Also, reading the patch I feel like I finally understand what a parse tree filter can/should look like.) Should org-export--remove-uninterpreted be added to the default value of org-export-filter-parse-tree-functions, rather than hard-coding it into org-export-as? Thanks for the quick patch, --=20 Aaron Ecay