From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>,
"'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 5809@debbugs.gnu.org
Subject: bug#5809: 23.1.94; cross-reference by anchor yields in accurate position
Date: Fri, 2 Apr 2010 07:17:35 -0700 [thread overview]
Message-ID: <422BAD8C75BE4F5BAE608BD47A355EFF@us.oracle.com> (raw)
In-Reply-To: <83sk7ewcvz.fsf@gnu.org>
> > > Here's another, perhaps better idea: how about if, instead of
> > > inserting breadcrumbs as text into the buffer, we put an
> > > overlay there with a display property whose value is the
> > > breadcrumbs as a string?
> > > This way, buffer positions are not affected at all.
> >
> > That was my thought as well, but then you can't "click" on
> > breadcrumbs with the keyboard any more.
>
> "Clicking" on breadcrumbs with a keyboard is the same as typing "u",
> so I don't see this as a loss. And if we think this _is_ a loss, we
> could add a new feature. Or maybe using the `cursor' property on the
> overlay will do the trick even without any new features.
Obviously, the ideal situation will be if both (a) breadcrumbs function fully
and (b) cross references and other features that reference positions function
accurately. That's what we're looking for, and that quest is good.
If, however, we ultimately find we need to, or decide to, settle for something
less than ideal, then there are different desirable qualities that could be
dropped. IOW it would be a trade-off.
I would just point out that things such as cross references are not completely
broken by breadcrumbs, IIUC. You are taken to the correct node in all cases, I
believe. Point is just not always moved to the exact location we would like - it
is sometimes moved nearby.
It might be decided that always respecting destination position exactly is a
must-have or is considered more important than the convenience (in terms of
orientation/help and navigation) of breadcrumbs. But let's at least be aware
that a trade-off is involved. It should not be a foregone conclusion to toss out
the baby with the bathwater.
Keep in mind too that in some documentation systems, which don't even have the
fine-grained "node" size of Info (on average), cross references generally do not
take you to an exact destination position. They just get you to the appropriate
section.
next prev parent reply other threads:[~2010-04-02 14:17 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 [this message]
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
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=422BAD8C75BE4F5BAE608BD47A355EFF@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=5809@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).