<Tom Gillespie (mailto:tgb...@gmail.com)> writes: > If the default header closures are being evaluated before checking > whether they have been superseded by the headers on a block then that > is incorrect and they should not be evaluated until it is clear that > they are the value of the header for that block and have not been > superseded. > > > > > > > > > > > > > > > > Good point, Tom. I’m back from vacation on Wednesday and can take a detailed look at this behavior then. Matt
- Re: babel default header args as functions Matt Huszagh
- Re: babel default header args as functions Matt Huszagh
- Re: babel default header args as functions Bastien
- Re: babel default header args as functions Tom Gillespie
- Re: babel default header args as function... Huszaghmatt
- Re: babel default header args as function... Bastien
- Re: babel default header args as fun... Tom Gillespie
- Re: babel default header args as function... Matt Huszagh
- Re: babel default header args as fun... Tom Gillespie
- Re: babel default header args as... rey-coyrehourcq
- Re: babel default header arg... Matt Huszagh
- Re: babel default header arg... rey-coyrehourcq
- Re: babel default header arg... Matt Huszagh
- Re: babel default header args as functions stardiviner
- Re: babel default header args as functions Matt Huszagh