Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes:
A canonical DESCRIPTION is NOT available. (YET) The ANCHOR should
still get through to the `texi' file, right?
We can replace a silly behaviour with another silly one, yes. But is
there any non-silly one?
This is the output I see in
On Saturday 30 May 2015 01:49 PM, Nicolas Goaziou wrote:
Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes:
A canonical DESCRIPTION is NOT available. (YET) The ANCHOR should
still get through to the `texi' file, right?
We can replace a silly behaviour with another silly one, yes.
Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes:
How about @ref{orgtarget1}?
I'd rather not expose internals to the user. Also, displaying
orgtarget1 in an info file would be more confusing than helpful.
Anyway, I changed a bit the behaviour for targets. Let me know what you
think
ox-texinfo: Link to dedicated to target doesn't work
See the attached .org and .texi file.
bug-texinfo.org
Description: Lotus Organizer
\input texinfo@c -*- texinfo -*-
@c %**start of header
@setfilename ./bug-texinfo.info
@settitle bug-texinfo
@documentencoding UTF-8
@documentlanguage en
Hello,
Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes:
ox-texinfo: Link to dedicated to target doesn't work
The behaviour is correct here.
You are inserting a link to a target without a description. As in any
export back-end, Org tries to associate it to a number, in this case,
On Friday 29 May 2015 09:26 PM, Nicolas Goaziou wrote:
Hello,
Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes:
ox-texinfo: Link to dedicated to target doesn't work
The behaviour is correct here.
You are inserting a link to a target without a description. As in any
export
