Re: [export] org-export-with-* bugs

[Nicolas Goaziou <n.goaziou@gmail.com>]

Hello,

Aaron Ecay <aaronecay@gmail.com> writes:

> 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'll ask the question in a separate thread.

> (fixed-width is one of the branches in the ‘case’ form in the new
> code...?)

Indeed. I attached the draft, not the real patch. I committed the
latter.

> I can confirm the fix.  It looks like the new mechanism is equivalent to
> a parse tree filter.

It is exactly a parse tree filter.

> 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?

No, it shouldn't. `org-export-filter-parse-tree-functions' is meant for
user's consumption. For example, export back-end have their own way to
add such a filter without clobbering the variable. In this case, the
implemented behaviour is clearly not optional, so it is logically
hard-coded.

Thank you for reporting the problem.


Regards,

-- 
Nicolas Goaziou