From: Vaidheeswaran C <vaidheeswaran.chinnaraju@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: ox-texinfo: Link to dedicated to target doesn't work
Date: Sat, 30 May 2015 14:06:22 +0530 [thread overview]
Message-ID: <mkbsru$dt9$1@ger.gmane.org> (raw)
In-Reply-To: <87siaexysv.fsf@nicolasgoaziou.fr>
On Saturday 30 May 2015 01:49 PM, Nicolas Goaziou wrote:
> Vaidheeswaran C <vaidheeswaran.chinnaraju@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?
Displaying a silly link is a call for an action (to fix). So, from
fixability perspective, having a silly anchor is better than pruning
it from output.
>> > This is the output I see in other backends (that support anchors).
>> >
>> > HTML:
>> >
>> > <p>
>> > Jump to <a href="#orgtarget1">No description for this link</a>.
>> > </p>
> The example above is a bit misleading because a description is not
> mandatory. In your situation, Option "num:t" would be sufficient to
> produce something.
I understand that the error is in the OPTIONs that I have and I need
to fix the Org file. Your argument is sound. (BUT) Having some
feedback that something is amisss is always desirable.
>> > LaTeX:
>> >
>> > Jump to \ref{orgtarget1}.
> If you look at it, this will not appear in the (PDF) output as there's
> nothing to refer to, much like what happens in ox-texinfo.
I see a red box (which is an urgent call for action).
> In any case, what exactly do you suggest in this situation, i.e., what
> should be displayed?
How about @ref{orgtarget1}?
----------------------------------------------------------------
ps: I can send in fixes. I have a copyright assignment. WDYT?
next prev parent reply other threads:[~2015-05-30 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 11:45 ox-texinfo: Link to dedicated to target doesn't work Vaidheeswaran C
2015-05-29 15:56 ` Nicolas Goaziou
2015-05-30 2:23 ` Vaidheeswaran C
2015-05-30 8:19 ` Nicolas Goaziou
2015-05-30 8:36 ` Vaidheeswaran C [this message]
2015-05-30 11:59 ` Nicolas Goaziou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='mkbsru$dt9$1@ger.gmane.org' \
--to=vaidheeswaran.chinnaraju@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).