From: Juri Linkov <juri@jurta.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: Info-build-node-completions has an extra `*' node
Date: Mon, 18 Feb 2008 02:29:19 +0200 [thread overview]
Message-ID: <87k5l3cdk0.fsf@jurta.org> (raw)
In-Reply-To: <008301c871c1$9f45d5c0$2d58908d@us.oracle.com> (Drew Adams's message of "Sun, 17 Feb 2008 16:02:58 -0800")
>> Please read the Info manual at (info "(info) Go to node") that says:
>>
>> The node name `*' specifies the whole file. So you can
>> look at all of the current file by typing `g*<RET>' or
>> all of any other file with `g(FILENAME)*<RET>'.
>
> I see. Guess I haven't read the Info manual in a long time. Out of
> curiosity, why was this feature added? What is the need that it satisfies?
This feature is from prehistoric times. It was already in the revision 1.1.
> And why is only `*' written in the mode line as the node name, rather than,
> say, `*** All Nodes ***' or `*** Whole Manual ***' (the `***' or something
> similar indicating that this is not just a node name). I'm afraid that `*'
> is not very noticeable in the mode line. There are already other `*' there,
> so you see, for example, `*info* (emacs) *'.
I guess that's because the name displayed in the mode line should be the
same as provided in the completion for consistency.
> And it is not immediately obvious that the entire manual is in fact visible.
> I thought that it had just revisited the current node, until I scrolled a
> bit and noticed that from the node headers that it was widened.
>
> Someone falling into this state by accident might well get confused, IMO.
> And `*' is the first completion candidate listed in *Completions*.
Maybe we should add an explanation text to the completion candidate like
e.g. `* (all nodes)'. And accept also `*' but don't display it in the
completion list.
> It might seem cute that `*' is the name for this pseudo-node (a wildcard,
> presumably), but the behavior and meaning are not obvious. Why `go to node'
> would have an alternative action of `show all nodes' is not clear to me -
> why associate this behavior with `Info-goto-node'? I suppose you'll say that
> that's what we do for wildcards with `find-file'.
Yes, this looks like wildcards.
> It's also not obvious how to get out of this view-whole-raw-info-file mode,
> once you fall into the black hole. Things like `C-l' and `u' (Node has no
> Up) don't help.
>
> It turns out that using `g' again, and picking some real node name this
> time, will restore Info to its normal self (whew!). There might be
> additional ways to get back to normal; I don't know.
>
> But I don't think it is obvious, and I do think it is potentially confusing.
> At the very least, a message should inform the user: (a) what has happened,
> and (b) how to get back to normal.
Displaying something like `all nodes' in the mode line would inform about
what has happened, but I have no idea how it could inform how to get back.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2008-02-18 0:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 22:25 Info-build-node-completions has an extra `*' node Drew Adams
2008-02-17 22:34 ` Drew Adams
2008-02-17 23:05 ` Bastien
2008-02-17 23:22 ` Juri Linkov
2008-02-17 23:53 ` Bastien Guerry
2008-02-18 0:27 ` Juri Linkov
2008-02-18 0:56 ` Bastien Guerry
2008-02-18 23:54 ` Juri Linkov
2008-02-19 0:48 ` Bastien
2008-02-21 19:24 ` Drew Adams
2008-02-18 0:02 ` Drew Adams
2008-02-18 0:29 ` Juri Linkov [this message]
2008-02-18 0:54 ` Bastien Guerry
2008-02-18 1:27 ` Drew Adams
2008-02-18 3:37 ` Miles Bader
2008-02-18 4:12 ` David De La Harpe Golden
2008-02-18 11:56 ` Bastien Guerry
2008-02-18 23:55 ` Juri Linkov
2008-02-18 17:31 ` Richard Stallman
2008-02-18 17:40 ` Drew Adams
2008-02-19 15:45 ` Richard Stallman
2008-02-19 21:35 ` Stefan Monnier
2008-02-20 3:23 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k5l3cdk0.fsf@jurta.org \
--to=juri@jurta.org \
--cc=drew.adams@oracle.com \
--cc=emacs-pretest-bug@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.