From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Xue Fuqiao <xfq.free@gmail.com>
Cc: eggert@cs.ucla.edu, kjambunathan@gmail.com, emacs-devel@gnu.org
Subject: RE: C-h r and Images
Date: Tue, 3 Sep 2013 09:34:51 -0700 (PDT) [thread overview]
Message-ID: <0b0e7cc8-6de6-446e-88fe-6b332c1e63b5@default> (raw)
In-Reply-To: <<83ioyhdhg7.fsf@gnu.org>>
> > > What's more, it would be helpful to hyperlink directly to an explanation
> > > of the term in question, rather than just saying "which see" or some
> > > such English alternative to "q.v."
> >
> > I made a patch for it. See bug#15254.
>
> Thanks. However, I'm not sure doing this is useful. The Glossary is
> a long series of short paragraphs, each one explaining one term. What
> your patch does is add a cross-reference to many of these short
> paragraphs, which makes those paragraphs longer and more complex to
> read and grasp at first glance. OTOH, since the terms are listed in
> alphabetic order, it is quite easy to find a given term, even if you
> just scroll and don't use the search commands.
>
> So my take of this is that on balance this is not useful.
I haven't looked at the patch itself. But the idea should be, if
possible, to have inline xrefs (links). That is, not add any extra text
(e.g. "See"), but just turn the term used in the text into a link to its
own definition.
That's pretty common in glossaries these days (and in indexes, when
referring to another index entry).
And yes, it's a lot easier to click (or hit `RET' on) a term to look at
its definition, and then click `Back' (or hit `l') to get back to where
you were, than it is to scroll down to find its definition and then
scroll back and find where you were.
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?
next prev parent reply other threads:[~2013-09-03 16:34 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 [this message]
2013-09-03 20:37 ` Juri Linkov
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=0b0e7cc8-6de6-446e-88fe-6b332c1e63b5@default \
--to=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).