From: Matthew Henry <mcthenry@gmail.com>
To: 37086@debbugs.gnu.org
Subject: bug#37086: Guile Ice-9 Readline with-readline-completion-function
Date: Mon, 19 Aug 2019 13:36:26 -0400 [thread overview]
Message-ID: <CAFZHh1qSRxn6nVj4E0KAUFU2aXaAHdZ86cpv9EBgvqnSGrW0rQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
Seen in: guile (GNU Guile) 2.2.4
When using the with-readline-completion-function, the passed readline
uses the default (apropos) completion function instead of the one
provided to with-readline-completion-function.
I believe that this is because root/guile-readline/ice-9/readline.scm
has defined with-readline-completion-function as a function instead of
as a macro. The readline provided in thunk is executed before the
body of with-readline-completion-function executes and overrides
*readline-completion-function*.
As an aside, I think the API would be better if the completion
function could be provided to readline directly.
Attached is a sample program.
Below is sample output of a run of the attached program. You can see
that it's autocompleting Guile functions and variables (the default
apropos completion) rather than the provided one which should have had
only 3 options with just one starting in "th".
;;;;;;;;;;;;;;;;;;;;;;;;;;;
Prompt:
Display all 1859 possibilities? (y or n)
Prompt: th
the-eof-object the-scm-module thread-exited? thunk?
the-root-module thread? throw
Prompt: th
[-- Attachment #2: readline-completion-bug.scm --]
[-- Type: application/octet-stream, Size: 142 bytes --]
(use-modules (ice-9 readline))
(with-readline-completion-function
(make-completion-function '("one" "two" "three"))
(readline "Prompt: "))
next reply other threads:[~2019-08-19 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 17:36 Matthew Henry [this message]
2019-08-20 0:12 ` bug#37086: Guile Ice-9 Readline with-readline-completion-function Matthew Henry
2019-08-20 3:00 ` Mark H Weaver
2019-08-20 11:35 ` Matthew Henry
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFZHh1qSRxn6nVj4E0KAUFU2aXaAHdZ86cpv9EBgvqnSGrW0rQ@mail.gmail.com \
--to=mcthenry@gmail.com \
--cc=37086@debbugs.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.
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).