Hello, Bastien <b...@altern.org> writes:
> the attached (dirty) patch fixes it. It's clearly not the right > approach, though. I hope Nicolas can have a look soon, as the problem > affect all uses of snippets in macros. What about the following patch? The export framework usually treats differently empty string from nil output. Only in the former blank lines/white spaces are preserved. With this patch it will not be possible anymore to make this distinction with export snippets. What do you think? I'll add some tests in test-ox.el if this patch is to be applied. Regards, -- Nicolas Goaziou
>From 9fed50f6760aa34a426981d3606285c090ffd5bd Mon Sep 17 00:00:00 2001 From: Nicolas Goaziou <n.goaz...@gmail.com> Date: Thu, 21 Mar 2013 20:08:24 +0100 Subject: [PATCH] ox: White spaces after export snippets are never ignored * lisp/ox.el (org-export-data): White spaces after export snippets are never ignored. Back-end developers should pay attention to the fact that white spaces before and after an ignored export snippet now are accumulated in the output. --- lisp/ox.el | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/lisp/ox.el b/lisp/ox.el index a545bb9..160f73f 100644 --- a/lisp/ox.el +++ b/lisp/ox.el @@ -2062,8 +2062,12 @@ Return transcoded string." (eq (plist-get info :with-archived-trees) 'headline) (org-element-property :archivedp data))) (let ((transcoder (org-export-transcoder data info))) - (and (functionp transcoder) - (funcall transcoder data nil info)))) + (or (and (functionp transcoder) + (funcall transcoder data nil info)) + ;; Export snippets never return a nil value so + ;; that white spaces following them are never + ;; ignored. + (and (eq type 'export-snippet) "")))) ;; Element/Object with contents. (t (let ((transcoder (org-export-transcoder data info))) -- 1.8.2
