From: Aaron Ecay <firstname.lastname@example.org> To: Nicolas Goaziou <email@example.com>, firstname.lastname@example.org Subject: Re: Bug in new exporter with babel blocks Date: Thu, 21 Feb 2013 13:11:09 -0500 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Nicolas, Thank you for your explanations, which were very helpful. 2013ko urtarrilak 23an, Nicolas Goaziou-ek idatzi zuen: > You needn't. org-exp-blocks functionalities are supported by the new > exporter out of the box. Can you say more about this? I looked for but did not find a replacement to the org-export-blocks variable (an alist associating block types with functions to export them). I found it very easy to hook into the new exporter, but perhaps I missed something? > Special blocks are de facto, recursive, much like drawers. Their > contents have to be parsed. For parsing, yes. But for export I want a way to say “I don’t care what Org thinks the export of this block is. Give me the raw contents, and I will tell you what the export should be.” This is how the ditaa special-block code used to work; I see that it has now morphed into a babel language, which makes some kind of sense. I’m not sure it does in general. My use case is glossed examples for linguistics: my special block contains three lines, which are a sentence in a foreign language and a translation. By inserting markup in a way which is easy to automate, you can get LaTeX to align the words of one language with the words of the other. I don’t want any org processing of the text of the examples: it might contain backslashes, stars, etc., all of which should be passed verbatim to LaTeX. This does not feel like source code, it cannot be evaluated or tangled, I would not want these blocks to be included in org-babel-next-src-block, etc. >> I’d also be happy to discover another, better way of getting the raw >> text content of the special-block that doesn’t succumb to this >> problem. > > If you must, you can try: > > (org-element-interpret-data (org-element-contents special-block)) > > from `org-e-latex-special-block'. I would up patching org-elements to add a :contents property to special-block elements, which is populated when parsing the original buffer (and thus dodges the different-buffer-for-export problem). I can then retrieve this in my export backend function. It is a very simple patch: -----------cut-here----------- diff --git i/lisp/org-element.el w/lisp/org-element.el index 3dc1e72..b67e5e6 100644 --- i/lisp/org-element.el +++ w/lisp/org-element.el @@ -1389,6 +1389,9 @@ Assume point is at the beginning of the block." :hiddenp hidden :contents-begin contents-begin :contents-end contents-end + :contents (and contents-begin contents-end + (buffer-substring-no-properties + contents-begin contents-end)) :post-blank (count-lines pos-before-blank end) :post-affiliated post-affiliated) (cdr affiliated))))))))) -----------cut-here----------- Is including support for special blocks that should be exported “raw” a compelling reason to install such a patch? I think the only downside would be increased memory usage/decreased speed for parsed objects (since they are now storing an extra string), but I think that would be very small (though I haven’t benchmarked anything). Thanks, -- Aaron Ecay
next prev parent reply other threads:[~2013-02-21 18:11 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-22 21:54 Aaron Ecay 2013-01-23 13:28 ` Nicolas Goaziou 2013-02-21 18:11 ` Aaron Ecay [this message] 2013-04-20 19:32 ` Nicolas Goaziou
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Bug in new exporter with babel blocks' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).