From: Juri Linkov <juri@jurta.org>
To: Bastien Guerry <Bastien.Guerry@ens.fr>
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 02:27:05 +0200 [thread overview]
Message-ID: <874pc7f7ta.fsf@jurta.org> (raw)
In-Reply-To: <87bq6fp2bz.fsf@bzg.ath.cx> (Bastien Guerry's message of "Sun, 17 Feb 2008 23:53:20 +0000")
> 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.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2008-02-18 0:27 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 [this message]
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
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=874pc7f7ta.fsf@jurta.org \
--to=juri@jurta.org \
--cc=Bastien.Guerry@ens.fr \
--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.