From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Re: breadcrumbs for Info . . . . . .
Date: Fri, 13 Jun 2008 10:43:15 +0200 [thread overview]
Message-ID: <87hcbxd8t8.fsf@ambire.localdomain> (raw)
In-Reply-To: <002401c8cd1f$98631650$0200a8c0@us.oracle.com> (Drew Adams's message of "Thu, 12 Jun 2008 23:34:55 -0700")
() "Drew Adams" <drew.adams@oracle.com>
() Thu, 12 Jun 2008 23:34:55 -0700
You can think of the breadcrumbs line as part of an extended
header area. (And you might even want to remove the Up link
from the header now, since it is no longer needed - the
breadcrumbs subsume Up.)
To me this says that breadcrumbs should be grafted onto Up,
rather than being a separate feature. From user pov, the NEWS
would not be:
New Info sub-feature: breadcrumbs [...]
but rather:
New Info sub-feature: Info "Up" extension. MB3 on the "Up" link
now displays a menu which lets you "navigate" (urgh) directly to
an ancestor node of the current node. From the keyboard, there
is a new command Info-skip-up, which queries you (w/ completion)
for an ancestor node to jump to... [etc. The idea is that mouse
or keyboard eventually do the same thing.]
Bias note: personally, i dislike features that use screen space.
If there is another line taken for breadcrumbs, i will find a way
to remove it.
thi
next prev parent reply other threads:[~2008-06-13 8:43 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 23:52 breadcrumbs for Info . . . . . Drew Adams
2008-06-11 0:04 ` Juri Linkov
2008-06-11 3:18 ` Drew Adams
2008-06-11 9:34 ` Juri Linkov
2008-06-11 13:46 ` Drew Adams
2008-06-11 18:59 ` Eli Zaretskii
2008-06-11 22:40 ` Juri Linkov
2008-06-12 2:01 ` Miles Bader
2008-06-12 22:42 ` Drew Adams
2008-06-13 3:27 ` Stefan Monnier
2008-06-13 6:34 ` Drew Adams
2008-06-13 8:43 ` Thien-Thi Nguyen [this message]
2008-06-13 13:55 ` Drew Adams
2008-06-13 17:17 ` Thien-Thi Nguyen
2008-06-13 17:52 ` Drew Adams
2008-06-13 19:55 ` Thien-Thi Nguyen
2008-06-13 20:10 ` Drew Adams
2008-06-15 18:19 ` Juri Linkov
2008-06-13 14:05 ` Stefan Monnier
2008-06-13 15:12 ` Drew Adams
2008-06-13 17:16 ` Stefan Monnier
2008-06-13 18:32 ` Thien-Thi Nguyen
2008-06-14 9:47 ` Eli Zaretskii
2008-06-14 10:01 ` Thien-Thi Nguyen
2008-06-13 13:58 ` Stefan Monnier
2008-06-13 15:11 ` Drew Adams
2008-06-13 20:34 ` Stefan Monnier
2008-06-13 22:11 ` Drew Adams
2008-06-13 22:44 ` Stefan Monnier
2008-06-14 9:45 ` Drew Adams
2008-06-14 16:16 ` Stefan Monnier
2008-06-14 17:24 ` Drew Adams
2008-06-14 18:04 ` Stefan Monnier
2008-06-15 0:27 ` Juri Linkov
2008-06-15 7:33 ` Drew Adams
2008-06-15 18:23 ` Juri Linkov
2008-06-15 19:46 ` Drew Adams
2008-06-15 0:28 ` Juri Linkov
2008-06-15 2:04 ` Stefan Monnier
2008-06-15 18:18 ` Juri Linkov
2008-06-15 7:55 ` Drew Adams
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=87hcbxd8t8.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.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).