[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#67210: 30.0.50; completing-read with REQUIRE-MATCH=t can sometimes r
From: |
Stefan Monnier |
Subject: |
bug#67210: 30.0.50; completing-read with REQUIRE-MATCH=t can sometimes return a non-match |
Date: |
Thu, 16 Nov 2023 10:04:51 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
>> Or perhaps completion-emacs22-try-completion is violating the spec of
>> completion-try-completion, and should be returning nil in this case?
The "emacs22" style disregards the text after point to compute the
completions, so "foo" would be a valid return value as well, but indeed
t seems wrong because that should apply to the complete input.
Stefan
- bug#67210: 30.0.50; completing-read with REQUIRE-MATCH=t can sometimes return a non-match, Spencer Baugh, 2023/11/15
- bug#67210: 30.0.50; completing-read with REQUIRE-MATCH=t can sometimes return a non-match, Drew Adams, 2023/11/15
- bug#67210: 30.0.50; completing-read with REQUIRE-MATCH=t can sometimes return a non-match, Eli Zaretskii, 2023/11/16
- bug#67210: 30.0.50; completing-read with REQUIRE-MATCH=t can sometimes return a non-match,
Stefan Monnier <=
- bug#67210: 30.0.50; completing-read with REQUIRE-MATCH=t can sometimes return a non-match, Spencer Baugh, 2023/11/16
- bug#67210: 30.0.50; completing-read with REQUIRE-MATCH=t can sometimes return a non-match, Stefan Monnier, 2023/11/16
- bug#67210: 30.0.50; completing-read with REQUIRE-MATCH=t can sometimes return a non-match, Stefan Monnier, 2023/11/17
- bug#67210: 30.0.50; completing-read with REQUIRE-MATCH=t can sometimes return a non-match, Spencer Baugh, 2023/11/17
- bug#67210: 30.0.50; completing-read with REQUIRE-MATCH=t can sometimes return a non-match, Stefan Monnier, 2023/11/17