From: Juri Linkov <juri@jurta.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 14717@debbugs.gnu.org
Subject: bug#14717: 24.3.50; Info-try-follow-nearest-node misses some footnotes
Date: Thu, 27 Jun 2013 02:39:07 +0300 [thread overview]
Message-ID: <8738s4jvc4.fsf@mail.jurta.org> (raw)
In-Reply-To: <87vc52599u.fsf@rosalinde.fritz.box> (Stephen Berman's message of "Tue, 25 Jun 2013 20:34:53 +0200")
> 0. emacs -Q
> 1. Type `C-h i m Elisp RET m Using Interactive RET TAB TAB TAB' to put
> point on the left parent of the reference mark for footnote (1) in
> this node.
> 2. Type RET, expecting to jump to the footnote, but instead:
> => user-error: No such node or anchor: It may be a string; its contents
> are a sequence of elements
>
> The following patch makes the footnote search and
> hence jumping to the footnote in that node succeed
Thanks, your patch correctly fixes the bug, I recommend to commit it.
BTW, if you are interested what I'm trying to do in bug#14670
where I renamed the text property of footnotes from `link' to `shr-url'
is to support shr-url links in Info. The value of the text properly
`shr-url' is the target of the link. The problem is how to address
a footnote? Maybe add a function that finds a footnote. But I'm afraid
that supporting an arbitrary function on the text properly `shr-url'
is too unsafe. So `shr-url' should contain only a string. The question
is in what format to specify a link to a footnote. Currently it has
the value `t'. Perhaps as a string it could contain a line number
of the footnote like "(elisp) Using Interactive (line 42)".
next prev parent reply other threads:[~2013-06-26 23:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 18:34 bug#14717: 24.3.50; Info-try-follow-nearest-node misses some footnotes Stephen Berman
2013-06-26 23:39 ` Juri Linkov [this message]
2013-06-27 9:37 ` Stephen Berman
2013-06-28 21:50 ` Juri Linkov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8738s4jvc4.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=14717@debbugs.gnu.org \
--cc=stephen.berman@gmx.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.