GNU bug report logs -
#27193
25.2; tmm should use completing-read-default
Previous Next
Reported by: Ryan <rct <at> thompsonclan.org>
Date: Fri, 2 Jun 2017 04:52:01 UTC
Severity: minor
Tags: patch
Found in version 25.2
Fixed in version 26.1
Done: Glenn Morris <rgm <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
On Fri, Jun 2, 2017 at 6:19 PM Drew Adams <drew.adams <at> oracle.com> wrote:
> Ido's completion behavior is as far from that of
> vanilla `completing-read' as is Tmm's completion behavior
> ("the result").
>
This is kind of my point. If someone calls ido-completing-read, you
wouldn't expect it to do something different based on the value of
completing-read-function, even if it ido used completing-read internally
(which it might have actually done in the past, but currently does not),
because by calling ido-completing-read the code has already specified it
wants ido completion. Similarly, tmm is implementing a very different
behavior from completing-read that is only recognizable as regular
completion if you specifically go looking for leaks in the abstraction, and
for the same reason I don't think tmm should be paying attention to
completing-read-function.
[Message part 2 (text/html, inline)]
This bug report was last modified 7 years and 353 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.