From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>
Cc: 5809@debbugs.gnu.org
Subject: bug#5809: 23.1.94; cross-reference by anchor yields in accurate position
Date: Mon, 5 Apr 2010 10:12:44 -0700 [thread overview]
Message-ID: <0E46F93610574883ACE7EDAA6B791B84@us.oracle.com> (raw)
In-Reply-To: <871veum52b.fsf@mail.jurta.org>
> No need to blindly trying to click all links. You can open the file
> `info/elisp' and count all strings that start with "Ref:"
> (they are anchors that put the cursor to a mid-node position).
>
> There are 66 lines with "Ref:" (that fail to go directly to the
> appropriate place) and 839 lines with "Node:" (that succeed since
> they put the cursor to the beginning of the node).
>
> The ratio of 66 to 839 is 8%. So you guess of 10% is closer to the
> actual percentage.
Thanks. I wasn't aware of that. Now we know. Neither "all the time" nor "very
rare". At least in terms of _numbers_ of links (see #2 below).
1. But what do you mean here by "fail to go directly to the appropriate place"?
As I pointed out, failing to go to the precise location is not a problem in the
vast majority of cases, since the link still takes you to the appropriate
paragraph or correct 1-3 line description. Does your measure take that into
account?
IOW, even if 10% of the links do not behave precisely, but 99.9% of those
fail-to-go-directly links still get you to the correct paragraph (or correct 1-2
line function/var description), then the 10% number is far too high as a measure
of the real problem.
2. I'm still assuming, based on experience, that it is mainly the index links
that target mid-node locations. So a secondary question would be how often the
different kinds of links are followed in practice - e.g. index vs other links.
If there is a significant difference (either way), that could be important. This
is a user-practice question, which cannot be answered by counting links.
I myself use the index a lot, at least via `i'. I think it's important that
index links actually take you where they should. But if users generally use
index links less than text-body links, then that reduces the practical problem
still further.
next prev parent reply other threads:[~2010-04-05 17:12 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 9:58 bug#5809: 23.1.94; cross-reference by anchor yields in accurate position Eli Zaretskii
2010-03-31 11:17 ` Eli Zaretskii
2010-03-31 15:08 ` Juri Linkov
2010-03-31 15:55 ` Eli Zaretskii
2010-04-01 18:06 ` Juri Linkov
2010-04-01 18:13 ` Eli Zaretskii
2010-04-01 18:30 ` Juri Linkov
2010-04-01 20:22 ` Eli Zaretskii
2010-04-01 20:49 ` Eli Zaretskii
2010-04-01 21:10 ` Juri Linkov
2010-04-01 22:16 ` Stefan Monnier
2010-04-02 7:07 ` Eli Zaretskii
2010-04-02 14:17 ` Drew Adams
2010-04-02 14:39 ` Eli Zaretskii
2010-04-02 15:26 ` Drew Adams
2010-04-04 20:39 ` Drew Adams
2010-04-04 20:47 ` Eli Zaretskii
2010-04-04 22:51 ` Drew Adams
2010-04-04 23:58 ` Juri Linkov
2010-04-05 7:01 ` Drew Adams
2010-04-05 16:42 ` Juri Linkov
2010-04-05 20:11 ` Stefan Monnier
2010-04-05 23:17 ` Drew Adams
2010-04-06 5:49 ` Drew Adams
2010-04-06 17:46 ` Drew Adams
2010-04-05 16:45 ` Juri Linkov
2010-04-05 17:12 ` Drew Adams [this message]
2010-04-05 21:55 ` Eli Zaretskii
2010-04-05 6:38 ` Drew Adams
2010-04-02 16:14 ` Juri Linkov
2010-04-02 16:31 ` Drew Adams
2010-04-02 17:41 ` Eli Zaretskii
2010-04-02 18:01 ` Stefan Monnier
2010-04-02 23:11 ` Juri Linkov
2010-04-03 22:04 ` Juri Linkov
2010-04-04 6:12 ` Eli Zaretskii
2010-04-04 11:07 ` Juri Linkov
2010-04-04 12:12 ` Eli Zaretskii
2010-04-04 23:51 ` Juri Linkov
2010-04-05 5:26 ` Eli Zaretskii
2010-04-04 14:31 ` Stefan Monnier
2010-04-04 23:52 ` Juri Linkov
2010-04-05 2:06 ` Stefan Monnier
2010-04-05 16:50 ` Juri Linkov
2010-04-05 20:09 ` Stefan Monnier
2010-04-05 22:17 ` Juri Linkov
2010-04-01 21:09 ` Juri Linkov
2010-04-02 18:03 ` Stefan Monnier
2010-04-25 18:28 ` Chong Yidong
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=0E46F93610574883ACE7EDAA6B791B84@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=5809@debbugs.gnu.org \
--cc=juri@jurta.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.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).