Hello,
Samuel Wales writes:
> What hook in the old exporter would be the closest equivalent?
>
>> (add-hook 'org-export-before-parsing-hook 'my-flush-old-comment-syntax)
Not equivalent, but close enough: `org-export-preprocess-hook'.
Regards,
--
Nicolas Goaziou
What hook in the old exporter would be the closest equivalent?
> (add-hook 'org-export-before-parsing-hook 'my-flush-old-comment-syntax)
Thanks.
Samuel
On 8/30/12, Nicolas Goaziou wrote:
> #+begin_src emacs-lisp
> (defun my-flush-old-comment-syntax (backend)
Thanks. I like your yes or no p idea.
> I am probably misunderstanding "bug 5". May you describe it again along
> with both the expected and actual behaviour in the situation?
It works no
Hello,
Samuel Wales writes:
> On 8/28/12, Nicolas Goaziou wrote:
>>> #bug 4: this paragraph now gets exported in HTML subtree
>>> #export, which will likely surprise many people who formerly
>>> #used "#" comments instead of "# " comments and don't
>>> #carefully check all output. they might
>
On 8/28/12, Nicolas Goaziou wrote:
>> #bug 4: this paragraph now gets exported in HTML subtree
>> #export, which will likely surprise many people who formerly
>> #used "#" comments instead of "# " comments and don't
>> #carefully check all output. they might
>> #even publish private information a
Hello,
Samuel Wales writes:
> Here are 6 bugs (or at least changes that might need to be
> documented) in Org commenting and filling.
>
> Context: commenting and filling used to use generic Emacs
> facilities, but now use Org-specific ones.
>
> original:
>
> ===
> x
>
> bug 1: the line above now
Here are 6 bugs (or at least changes that might need to be
documented) in Org commenting and filling.
Context: commenting and filling used to use generic Emacs
facilities, but now use Org-specific ones.
original:
===
x
bug 1: the line above now does not get commented even if
comment-empty-lines
