Hello,
Bastien writes:
>> 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?
>
>
Hi Nicolas,
Nicolas Goaziou writes:
> 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 thin
Hello,
Bastien 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 stri
Hello,
Bastien 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.
I don't have time to look at the problem right now. I will probably do
it sunday.
Thank yo
Hi Thomas,
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.
Thanks for reporting this,
Changes in master
Modified lisp/ox-html.el
diff --git a/lisp/ox-html.el b/lisp/o
Aloha Achim,
Achim Gratz writes:
> Thomas S. Dye writes:
>> Help?
>
> Nice riddle. But here's what I think is happening: your macro expansion
> ends with a texinfo export snippet. That export snippet is ignored by
> the the HTML backend as it should, but in doing so the post-blank that
> the e
Thomas S. Dye writes:
> Help?
Nice riddle. But here's what I think is happening: your macro expansion
ends with a texinfo export snippet. That export snippet is ignored by
the the HTML backend as it should, but in doing so the post-blank that
the export snippet has gobbled up greedily during par
Aloha all,
This Org source:
- {{{kbdkey(S-,TAB)}}} or {{{kbdspckey(C-u,TAB)}}}, ~org-global-cycle~ ::
yields this texinfo output:
@item @kbd{S-@key{TAB}} or @kbd{C-u @key{TAB}}, @code{org-global-cycle}
which looks fine in info:
`S-' or `C-u ', `org-global-cycle'
and in pdf:
S-TAB or C-u TA
