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. > > 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 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 ‘case’ form in the 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, -- Aaron Ecay
