From: Dmitry Gutov <dgutov@yandex.ru>
To: Drew Adams <drew.adams@oracle.com>,
Ryan Thompson <rct@thompsonclan.org>,
27193@debbugs.gnu.org
Subject: bug#27193: 25.2; tmm should use completing-read-default
Date: Sat, 3 Jun 2017 00:37:00 +0300 [thread overview]
Message-ID: <669d7dff-a4bf-75b2-1652-6217efb84c72@yandex.ru> (raw)
In-Reply-To: <6a2811d5-8a21-47a6-b416-41bda3e36f67@default>
On 6/3/17 12:25 AM, Drew Adams wrote:
> The case that needs to be made for your proposal is really (IMO) that
> there are /NO/ values of `completing-read-function', apart from
> `completing-read-default', which would be compatible with the tmm code.
That would be too strong.
> I don't think you can make that case. I sense you are extrapolating from
> your own particular use of `completing-read-function' (and similar uses).
This is ridiculous. If there are functions that adhere to the contract
of completing-read-function, and tmm can't work with them, tmm should
use completing-read-default, and that's that.
I'll install the submitted patch in a few days if someone doesn't beat
me to it.
> The result is not even recognizable as completing-read.
>
> I don't think so. Certainly no more unrecognizable than Ido...
You are mixing up concepts right and left. E.g. APIs with their callers.
next prev parent reply other threads:[~2017-06-02 21:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 4:50 bug#27193: 25.2; tmm should use completing-read-default Ryan
2017-06-02 15:26 ` Drew Adams
2017-06-02 17:37 ` Ryan Thompson
2017-06-02 20:45 ` Ryan Thompson
2017-06-02 21:25 ` Drew Adams
2017-06-02 21:37 ` Dmitry Gutov [this message]
2017-06-02 22:19 ` Drew Adams
2017-06-02 22:24 ` Dmitry Gutov
2017-06-02 23:08 ` Ryan Thompson
2017-06-02 23:10 ` Ryan Thompson
2017-06-02 22:52 ` Ryan Thompson
2017-06-03 0:15 ` Drew Adams
2017-06-03 0:02 ` Glenn Morris
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=669d7dff-a4bf-75b2-1652-6217efb84c72@yandex.ru \
--to=dgutov@yandex.ru \
--cc=27193@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=rct@thompsonclan.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.