Hi Jon,
Jonathan Leech-Pepin writes:
> Hi Tom,
>
> On 14 February 2013 12:02, Thomas S. Dye wrote:
>
>> Hi Jon,
>>
>> Jonathan Leech-Pepin writes:
>>
>> [...]
>>
>> Thanks. I've moved the anchors outside comments and all is well. In
>> fact, the entire manual now exports texinfo that makeinfo
Hi Tom,
On 14 February 2013 12:02, Thomas S. Dye wrote:
> Hi Jon,
>
> Jonathan Leech-Pepin writes:
>
> [...]
>
> Thanks. I've moved the anchors outside comments and all is well. In
> fact, the entire manual now exports texinfo that makeinfo compiles
> without any complaints.
>
>
That's great.
Hi Jon,
Jonathan Leech-Pepin writes:
> Hello Tom,
>
> On 13 February 2013 11:31, Thomas S. Dye wrote:
>
>> Aloha all,
>>
>> Currently, the texinfo exporter translates a dedicated target in a comment:
>>
>> # <>
>>
>> to this:
>>
>> @c <>
>>
>> It shouldn't need to be within a comment to work su
Hello Tom,
On 13 February 2013 11:31, Thomas S. Dye wrote:
> Aloha all,
>
> Currently, the texinfo exporter translates a dedicated target in a comment:
>
> # <>
>
> to this:
>
> @c <>
>
> It shouldn't need to be within a comment to work successfully in the
Texinfo exporter.
@anchor{} is not visi
t...@tsdye.com (Thomas S. Dye) writes:
> Nicolas Goaziou writes:
>
>> Hello,
>>
>> t...@tsdye.com (Thomas S. Dye) writes:
>>
>>> Currently, the texinfo exporter translates a dedicated target in a comment:
>>>
>>> # <>
>>
>> This isn't a target. This is a comment that contains some text looking
>>
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Currently, the texinfo exporter translates a dedicated target in a comment:
>>
>> # <>
>
> This isn't a target. This is a comment that contains some text looking
> like Org syntax.
>
OK. I see I have a note from yo
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> Currently, the texinfo exporter translates a dedicated target in a comment:
>
> # <>
This isn't a target. This is a comment that contains some text looking
like Org syntax.
> to this:
>
> @c <>
>
> I was expecting to see a texinfo anchor:
>
> @anc
Aloha all,
Currently, the texinfo exporter translates a dedicated target in a comment:
# <>
to this:
@c <>
I was expecting to see a texinfo anchor:
@anchor{x-export-to-odt}
There are a handful of these dedicated target comments cum anchors in the Org
mode manual. I believe all of them are in
