Eric Schulte writes:
> Rainer M Krug writes:
>
>> Charles Berry writes:
>>
>>> Eric Schulte gmail.com> writes:
>>>
Rainer M Krug krugs.de> writes:
> The error is back:
>
You say "back", was this error not present recently? If so could you
isolate th
Rainer M Krug writes:
> Charles Berry writes:
>
>> Eric Schulte gmail.com> writes:
>>
>>>
>>> Rainer M Krug krugs.de> writes:
>>>
>>> > The error is back:
>>> >
>>>
>>> You say "back", was this error not present recently? If so could you
>>> isolate the commit at which this error appeared?
Charles Berry writes:
> Eric Schulte gmail.com> writes:
>
>>
>> Rainer M Krug krugs.de> writes:
>>
>> > The error is back:
>> >
>>
>> You say "back", was this error not present recently? If so could you
>> isolate the commit at which this error appeared?
>>
>
> The bug seems to be in the u
Eric Schulte gmail.com> writes:
>
> Rainer M Krug krugs.de> writes:
>
> > The error is back:
> >
>
> You say "back", was this error not present recently? If so could you
> isolate the commit at which this error appeared?
>
The bug seems to be in the use of
(org-link-search heading)
I reported it some time ago but couldn't reproduce it later, so I reported it
fixed. Now I realized that the 'reproducible example' did not show the error as
the header names were different. So I do not know if it is a new error, but I
can check on Friday.
Cheers,
Rainer
Envoyé de mon iPhone
Rainer M Krug writes:
> The error is back:
>
You say "back", was this error not present recently? If so could you
isolate the commit at which this error appeared?
Thanks,
Eric
>
> When one header in a subtree which has the header argument
> :eval never
> has the same name as in a following su
The error is back:
When one header in a subtree which has the header argument
:eval never
has the same name as in a following subtree which should be evaluated on
export, the second subtree is not exported. When the name of the header
is changed, the subtree is exported as expected.
--8<
