Am 11. Februar 2021 um 21:12 Uhr +0100 schrieb Sébastien Miquel:
> The purpose of #+BIND is to set some variables in the copied buffer.
>
> Also, these variables are set after macro expansion (and
> org-export-before-parsing-hook).
Thanks for the information. If they are set after macro
M. ‘quintus’ Gülker writes:
Now I wonder whether #+BIND is more elegant. But my macro expansion
function modifies a buffer-local variable. Does #+BIND allow for that,
so that the changed value is available in the original org buffer?
The purpose of #+BIND is to set some variables in the
On Wednesday, 10 Feb 2021 at 22:43, Maxim Nikulin wrote:
> Concerning BIND, there was a topic a month ago that bind
> has to be enabled explicitly. Unsure if it makes parameter available
> early enough however:
My understanding is that it makes it available, i.e. in the sense that
it's simply not
Am 09. Februar 2021 um 14:21 Uhr +0100 schrieb Sébastien Miquel:
> Eric S Fraga writes:
> > I tried but this doesn't seem to be propagated to the export as the
> > export works on a copy of the buffer, not the buffer itself. That's
> > what #+BIND is for, supposedly...
>
> I think this buffer
On 09/02/2021 19:06, Eric S Fraga wrote:
On Tuesday, 9 Feb 2021 at 12:30, to...@tuxteam.de wrote:
Perhaps a file local variable?
I tried but this doesn't seem to be propagated to the export as the
export works on a copy of the buffer, not the buffer itself. That's
what #+BIND is for,
On Tuesday, 9 Feb 2021 at 14:21, Sébastien Miquel wrote:
> I think this buffer copy preserves local variables. I know I use a
> such a local variable and its value can be read during macro
> expansion.
It does. Not sure what happened but I thought setting a file
local variable was the first
Eric S Fraga writes:
I tried but this doesn't seem to be propagated to the export as the
export works on a copy of the buffer, not the buffer itself. That's
what #+BIND is for, supposedly...
I think this buffer copy preserves local variables. I know I use a such
a local variable and its
On Tuesday, 9 Feb 2021 at 12:30, to...@tuxteam.de wrote:
> Perhaps a file local variable?
Thank you.
I tried but this doesn't seem to be propagated to the export as the
export works on a copy of the buffer, not the buffer itself. That's
what #+BIND is for, supposedly...
I'll play some more.
On Tue, Feb 09, 2021 at 10:13:01AM +, Eric S Fraga wrote:
> Dear org mode users,
>
> I have a small elisp function that I use to process my org file before
> export to LaTeX or HTML, adding this function to
> org-export-before-parsing-hook. Briefly, the function exports the TBLFM
> lines so
Dear org mode users,
I have a small elisp function that I use to process my org file before
export to LaTeX or HTML, adding this function to
org-export-before-parsing-hook. Briefly, the function exports the TBLFM
lines so that the org table calculations can be inspected. This is for
pedagogical
10 matches
Mail list logo
