From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: zedzap@gmail.com, 3454@emacsbugs.donarmstrong.com
Subject: bug#3454: <SPC> when reading the emacs manual sometimes goes to the wrong node
Date: Thu, 04 Jun 2009 12:11:11 -0400 [thread overview]
Message-ID: <E1MCFX5-00028C-Kn@fencepost.gnu.org> (raw)
In-Reply-To: <jwvtz2wnfyd.fsf-monnier+emacsbugreports@gnu.org> (message from Stefan Monnier on Thu, 04 Jun 2009 12:06:12 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: 3454@emacsbugs.donarmstrong.com, Eli Zaretskii <eliz@gnu.org>
> Date: Thu, 04 Jun 2009 12:06:12 -0400
>
> Actually I think that SPC's behavior in index nodes is wrong.
> Basically, SPC currently presumes that info nodes linked by menus form
> a tree, and it is mostly true, but not for index menus.
Index is just a large menu; it's not easy to distinguish the two, and
the decision would be error-prone. We already tried to ``improve''
Info, and I cannot say that the result looks good.
I don't see why bother in this case: a human can always know that she
is in an index, and not use SPC near the end.
next prev parent reply other threads:[~2009-06-04 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1MBsYf-0002mJ-Tq@fencepost.gnu.org>
2009-06-03 5:40 ` bug#3454: <SPC> when reading the emacs manual sometimes goes to the wrong node Shannon Jones
2009-06-03 15:45 ` bug#3454: marked as done (<SPC> when reading the emacs manual sometimes goes to the wrong node) Emacs bug Tracking System
2009-06-03 23:41 ` Johan =?UTF-8?Q?Bockg=C3=A5rd
2009-06-03 18:15 ` bug#3454: <SPC> when reading the emacs manual sometimes goes to the wrong node Shannon Jones
2009-06-04 16:06 ` Stefan Monnier
2009-06-04 16:11 ` Eli Zaretskii [this message]
2009-06-04 18:37 ` Stefan Monnier
2009-06-08 18:26 ` bug#3454: <SPC> when reading the emacs manual sometimes goes to thewrong node 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=E1MCFX5-00028C-Kn@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=3454@emacsbugs.donarmstrong.com \
--cc=monnier@iro.umontreal.ca \
--cc=zedzap@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).