From: Bastien Guerry <Bastien.Guerry@ens.fr>
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: Mon, 18 Feb 2008 00:54:36 +0000 [thread overview]
Message-ID: <87mypznkxf.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87k5l3cdk0.fsf@jurta.org> (Juri Linkov's message of "Mon, 18 Feb 2008 02:29:19 +0200")
Juri Linkov <juri@jurta.org> writes:
>> 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.
Yes, this would be useful.
--
Bastien
next prev parent reply other threads:[~2008-02-18 0:54 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
2008-02-18 0:54 ` Bastien Guerry [this message]
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=87mypznkxf.fsf@bzg.ath.cx \
--to=bastien.guerry@ens.fr \
--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 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.