From: Juri Linkov <juri@jurta.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 12456@debbugs.gnu.org
Subject: bug#12456: 24.2.50; Completion in `Info-goto-node' (cross-manual jump)
Date: Sat, 29 Dec 2012 01:57:11 +0200 [thread overview]
Message-ID: <87han51zx8.fsf@mail.jurta.org> (raw)
In-Reply-To: <87bodfgntf.fsf@mail.jurta.org> (Juri Linkov's message of "Thu, 27 Dec 2012 23:57:04 +0200")
>> One question: if I do (from emacs -Q) `C-h r g ( e l i TAB TAB', I see
>> two completion candidates: "elisp" and "elisp.info". This is a bug,
>> no?
>
> I doubt its usefulness too because it doesn't allow TAB to add the
> closing paren automatically as it does for a single completion,
> but as a comment in `Info-read-node-name-2' says:
>
> ;; If the file name ends in a standard suffix,
> ;; add the unsuffixed name as a completion option.
>
> So code adds both "elisp.info" with a standard suffix ".info"
> and the unsuffixed name "elisp".
>
> This means this intentionally is a feature, and not a bug.
But this doesn't mean it is a good feature. Another similar command
`info-display-manual' doesn't add duplicates "elisp" and "elisp.info",
so when you do `M-x info-display-manual RET TAB' it displays a single
completion for every Info manual name without adding the suffix ".info".
next prev parent reply other threads:[~2012-12-28 23:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-16 17:59 bug#12456: 24.2.50; Completion in `Info-goto-node' (cross-manual jump) Dani Moncayo
2012-09-16 19:39 ` Dani Moncayo
2012-09-17 21:12 ` Stefan Monnier
2012-09-18 6:23 ` Eli Zaretskii
2012-09-18 12:22 ` Stefan Monnier
2012-09-18 13:52 ` Eli Zaretskii
2012-09-18 14:26 ` Dani Moncayo
2012-09-18 16:57 ` Stefan Monnier
2012-09-18 20:03 ` Juri Linkov
2012-12-15 15:30 ` Juri Linkov
2012-12-27 20:42 ` Juri Linkov
2012-12-27 21:37 ` Dani Moncayo
2012-12-27 21:57 ` Juri Linkov
2012-12-28 23:57 ` Juri Linkov [this message]
2012-12-29 0:24 ` Dani Moncayo
2012-12-29 21:59 ` Juri Linkov
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=87han51zx8.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=12456@debbugs.gnu.org \
--cc=dmoncayo@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).