Hello, Omid <omidl...@gmail.com> writes:
> I think #+INCLUDE: should be just that: Include whatever the user is > asking to. No header arguments dumps the file in Org (as it does now), > subject to the usual processing, and a header argument like html wraps > it in the appropriate delimiter, subject to processing according to > that delimiter. We don't need support for arbitrary blocks in keywords INCLUDE. Using actual blocks will work just fine: #+BEGIN_QUOTE #+INCLUDE: "file.org" #+END_QUOTE This is very regular: no need for redundancy in these cases. Though, it cannot work for verbatim blocks[1] for obvious reasons. That's why INCLUDE syntax provides parameters for both "example" and "src" blocks. At the moment, there's no support for export blocks. We just need to add that. Regards, [1] And verse blocks, but I'd rather put it aside for now. -- Nicolas Goaziou
