From: Juri Linkov <juri@jurta.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 10771@debbugs.gnu.org, Chong Yidong <cyd@gnu.org>
Subject: bug#10771: TAB completion for info-display-manual
Date: Sun, 02 Dec 2012 23:12:35 +0200 [thread overview]
Message-ID: <87boecqjzz.fsf@mail.jurta.org> (raw)
In-Reply-To: <8338zotlhq.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 02 Dec 2012 19:25:05 +0200")
> Because manuals loaded into my Info buffers do not necessarily reflect
> Info files on my disk.
Is this because you delete Info files from the disk leaving open
their Info buffers? I'm not sure whether additional complexity
is necessary to handle completion for such rare cases, but at least
the minibuffer should allow you to enter such manual names.
I mean changing the REQUIRE-MATCH arg of `completing-read' from t to nil,
so you can still enter these manual names like at the time when
this command accepted a plain string before the latest change.
=== modified file 'lisp/info.el'
--- lisp/info.el 2012-12-02 20:07:04 +0000
+++ lisp/info.el 2012-12-02 21:11:17 +0000
@@ -5138,7 +5138,7 @@ (defun info-display-manual (manual)
(apply-partially 'Info-read-node-name-2
Info-directory-list
(mapcar 'car Info-suffix-list))
- nil t))))
+ nil nil))))
(let ((blist (buffer-list))
(manual-re (concat "\\(/\\|\\`\\)" manual "\\(\\.\\|\\'\\)"))
(case-fold-search t)
next prev parent reply other threads:[~2012-12-02 21:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 6:36 bug#10771: TAB completion for info-display-manual Glenn Morris
2012-02-09 9:28 ` Juri Linkov
2012-02-09 18:42 ` Eli Zaretskii
2012-02-10 10:17 ` Juri Linkov
2012-12-02 6:44 ` Chong Yidong
2012-12-02 17:25 ` Eli Zaretskii
2012-12-02 21:12 ` Juri Linkov [this message]
2012-12-02 21:32 ` Eli Zaretskii
2012-12-02 21:57 ` Juri Linkov
2012-12-03 3:37 ` Eli Zaretskii
2012-12-03 6:57 ` Chong Yidong
2012-12-03 16:31 ` Eli Zaretskii
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=87boecqjzz.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=10771@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=eliz@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 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).