all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@jurta.org>
Cc: xfq.free@gmail.com, 13989@debbugs.gnu.org
Subject: bug#13989: Make Info support footnotes
Date: Wed, 20 Mar 2013 05:50:49 +0200	[thread overview]
Message-ID: <834ng620h2.fsf@gnu.org> (raw)
In-Reply-To: <87obefdnuq.fsf@mail.jurta.org>

> From: Juri Linkov <juri@jurta.org>
> Date: Wed, 20 Mar 2013 00:30:21 +0200
> Cc: 13989@debbugs.gnu.org
> 
> > And it's pretty straightforward to implement:
> 
> But footnotes are still not navigable.  Typing `TAB' should navigate
> to the next/previous footnote as it does for the cross-node references
> and URLs.
> 
> Since adding a footnote regexp to `Info-next-reference' will create
> false positives such as e.g. `TAB' will find plain text "(1)" and "(2)"
> in the node (info "(emacs) Copying"), a better approach would be
> to support text-property links like used in the *Help* buffers where
> links have a special text property that `TAB' (`forward-button')
> searches for to navigate to the next link.
> 
> These two approaches can co-exist in Info, so `TAB' will move point
> to the closest position found either by `re-search-forward' or
> `next-single-char-property-change'.
> 
> Later these text properties could be added to links in virtual nodes
> because this approach is more efficient and reliable.

What if the footnote style is set to 'Separate' in the Texinfo
sources?





  reply	other threads:[~2013-03-20  3:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-18 10:24 bug#13989: Make Info support footnotes Xue Fuqiao
2013-03-18 22:35 ` Juri Linkov
2013-03-19 22:30   ` Juri Linkov
2013-03-20  3:50     ` Eli Zaretskii [this message]
2013-03-20 23:05       ` Juri Linkov
2013-03-21  8:09         ` Xue Fuqiao

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=834ng620h2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=13989@debbugs.gnu.org \
    --cc=juri@jurta.org \
    --cc=xfq.free@gmail.com \
    /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.