From: Juri Linkov <juri@jurta.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: Xue Fuqiao <xfq.free@gmail.com>, Eli Zaretskii <eliz@gnu.org>,
eggert@cs.ucla.edu, kjambunathan@gmail.com, emacs-devel@gnu.org
Subject: Re: C-h r and Images
Date: Tue, 03 Sep 2013 23:37:43 +0300 [thread overview]
Message-ID: <87ob89k5ew.fsf@mail.jurta.org> (raw)
In-Reply-To: <0b0e7cc8-6de6-446e-88fe-6b332c1e63b5@default> (Drew Adams's message of "Tue, 3 Sep 2013 09:34:51 -0700 (PDT)")
> Now, if it is not possible today to have inline xrefs in Info then
> that's too bad. Then it's a tradeoff: Is the convenience of direct
> access worth the extra verbage ("See" or whatever) added?
Today it's possible to have inline xrefs like they are
implemented for footnotes. But the problem is how to
detect inline xrefs in Info files. I mean when
inline and non-inline xrefs are defined in the source as:
The bindings of all key sequences are recorded in the keymaps
(@pxref{Glossary---Keymap}). @xref{Keymaps}.
How to distinguish them in the Info output of makeinfo
and render them differently in the Info reader?
> How would that be done on parts of an image (which is just pixels)?
> Can we do (the equivalent of) image maps, letting users, in effect,
> click a callout (e.g., for "Mode Line"), to go to an appropriate part
> of the manual for more info about it (e.g., `(emacs) Mode Line'), or to
> provide a tooltip with a little related info?
Maybe sliced images could help to do such image maps where
anchors will be attached to sliced parts of an image.
next prev parent reply other threads:[~2013-09-03 20:37 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<87y57fe2ej.fsf@gmail.com>
[not found] ` <<831u57e089.fsf@gnu.org>
[not found] ` <<5224AEB3.5000508@cs.ucla.edu>
[not found] ` <<4884857e-3cd1-4b47-9949-6919c60f2186@default>
[not found] ` <<83txi3cih5.fsf@gnu.org>
2013-09-02 17:02 ` C-h r and Images Drew Adams
2013-09-02 17:39 ` Eli Zaretskii
[not found] ` <<878uzf5dvr.fsf@gmail.com>
[not found] ` <<50869c34-8cb2-477b-a6a8-a393abb76d12@default>
[not found] ` <<CAAF+z6EHgnt4Mbz8hHfv3csDUPYGvuNOQGKNB_AiNee7Umiahg@mail.gmail.com>
[not found] ` <<83ioyhdhg7.fsf@gnu.org>
2013-09-03 16:34 ` Drew Adams
2013-09-03 20:37 ` Juri Linkov [this message]
2013-09-04 5:47 ` Eli Zaretskii
2013-09-04 22:38 ` Xue Fuqiao
2013-09-04 22:41 ` Xue Fuqiao
2013-09-05 7:07 ` Eli Zaretskii
2013-09-06 10:53 ` Xue Fuqiao
2013-09-06 12:16 ` Eli Zaretskii
[not found] <<372ba59c-42be-463c-a69f-6b910d8cc40e@default>
[not found] ` <<83r4d7cecc.fsf@gnu.org>
2013-09-02 18:15 ` Drew Adams
2013-09-02 14:14 Jambunathan K
2013-09-02 15:01 ` Eli Zaretskii
2013-09-02 15:28 ` Paul Eggert
2013-09-02 15:38 ` Eli Zaretskii
2013-09-02 15:40 ` Eli Zaretskii
2013-09-02 21:34 ` Paul Eggert
2013-09-03 2:43 ` Eli Zaretskii
2013-09-03 3:18 ` Stephen J. Turnbull
2013-09-09 10:03 ` Stephen Berman
2013-09-09 14:07 ` Stefan Monnier
2013-09-09 15:03 ` Stephen Berman
2013-09-09 15:01 ` Andreas Schwab
2013-09-09 15:06 ` Stephen Berman
2013-09-16 12:11 ` Per Starbäck
2013-09-02 16:11 ` Eli Zaretskii
2013-09-02 15:44 ` Drew Adams
2013-09-02 16:10 ` Eli Zaretskii
2013-09-02 17:31 ` Jambunathan K
2013-09-02 17:41 ` Eli Zaretskii
2013-09-02 18:34 ` Jambunathan K
2013-09-02 18:10 ` Drew Adams
2013-09-02 19:37 ` Juri Linkov
2013-09-02 20:16 ` Drew Adams
2013-09-03 2:37 ` Kanthimathi R
2013-09-03 8:56 ` Xue Fuqiao
2013-09-03 14:41 ` Drew Adams
2013-09-03 15:59 ` Eli Zaretskii
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ob89k5ew.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=drew.adams@oracle.com \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kjambunathan@gmail.com \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.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).