From: Bastien <bzg@altern.org>
To: Juri Linkov <juri@jurta.org>
Cc: emacs-pretest-bug@gnu.org, Drew Adams <drew.adams@oracle.com>
Subject: Re: Info-build-node-completions has an extra `*' node
Date: Tue, 19 Feb 2008 00:48:33 +0000 [thread overview]
Message-ID: <87lk5h6aam.fsf@bzg.ath.cx> (raw)
In-Reply-To: <873arpn89f.fsf@jurta.org> (Juri Linkov's message of "Tue, 19 Feb 2008 01:54:28 +0200")
Juri Linkov <juri@jurta.org> writes:
>>>> I would prefer the completion to list the possible file names as it
>>>> lists the possible node names in a normal Info node, without the need
>>>> to enter a parenthesis first.
>>>
>>> This would break the standard format of the node name `(FILE)NODE'.
>>>
>>> `g' lists all node names (the virtual Info file `dir' has only one
>>> node `Top' so it is right for `g' to list only this single node.)
>>> And according to this format a file name should be inside parenthesis,
>>> so completion for the file name after parenthesis is more correct.
>>
>> What about putting an opening parenthesis in the default list of
>> completion for the (dir) buffer? For now the opening parenthesis is
>> like a secret key for those who know that the list of visible items
>> only reflects files, not real nodes.
>
> Why would someone normally want a completion on Info file names instead of
> Info manual names with typing `m TAB'?
I think this boils down to disambiguate what a "menu item" refers to.
In a manual, a menu item is a node; in (dir), a menu item is a really
a file name (a manual.)
My point is that, when listed in (dir), a manual looks like a node.
Hence the user might expect `Info-goto-node' to offer completion on
the manuals as well.
In fact, I find `Info-menu' and `Info-goto-node' to be a bit redundant,
and the fact that `Info-goto-node' is not helpful in (dir) doesn't help
the two commands to be less redundant.
But maybe I don't know info.el enough and I miss something.
--
Bastien
next prev parent reply other threads:[~2008-02-19 0:48 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 [this message]
2008-02-21 19:24 ` Drew Adams
2008-02-18 0:02 ` Drew Adams
2008-02-18 0:29 ` Juri Linkov
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
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=87lk5h6aam.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=drew.adams@oracle.com \
--cc=emacs-pretest-bug@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).