The following Org document exports to Texinfo '.texi’ in Orgmode
9.1.14 but fails under Orgmode 9.2 with the following error message:
'Cannot generate node name for type: src-block'
The source of the problem arises from commit `04f35fc473`. When the
changes are undone in that one commit, the
Hello:
I am seeking to find the right way to obtain identical output when exporting an
Org file into texinfo using the export menu from within the Org file as well as
from a Makefile using an Emacs batch script.
Currently I am using (org-export-to-file ‘texinfo “”) from within a
Makefile.
In Org 9.4, Manual section 11 Agenda Views, second to last paragraph, neither
of the referenced variables appears to exist. The manual should be updated; is
there a different mechanism for these actions now?
Regards,
Wesley
'(org-version)' produces:
9.4-41-g9bb930-elpaplus from org-plus-contrib-20201116
> On Nov 19, 2020, at 8:28 PM, Kyle Meyer wrote:
>
> wlharv...@mac.com writes:
>
>> In Org 9.4, Manual section 11 Agenda Views, second to last paragraph,
>> neither of the referenced variables appears to exist.
>
Hmm, I restarted Emacs, and the variables show up. My apologies. I upgraded a
day or two ago, but didn’t restart until now.
Wesley
> On Nov 19, 2020, at 8:28 PM, Kyle Meyer wrote:
>
> wlharv...@mac.com writes:
>
>> In Org 9.4, Manual section 11 Agenda Views, second to last paragraph,
>>
Is it possible to inject the value of a macro into code using a variable?
I set a macro called ‘version’ with a version number at the top of my .org
file. I would like to do something like this:
#+macro:version Version 0.2.5
#+name:code-name
#+begin_src js :tangle some-file.js :var
