From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Ryan Thompson Newsgroups: gmane.emacs.bugs Subject: bug#27193: 25.2; tmm should use completing-read-default Date: Fri, 02 Jun 2017 23:08:38 +0000 Message-ID: References: <7241c3bc-d7eb-4ce3-998e-dcc21d54ef7f@default> <6a2811d5-8a21-47a6-b416-41bda3e36f67@default> <669d7dff-a4bf-75b2-1652-6217efb84c72@yandex.ru> <236c968a-a11f-4a5a-88bc-f60edb50aa18@default> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a1144046875ab1a0551023ca9" X-Trace: blaine.gmane.org 1496444954 31768 195.159.176.226 (2 Jun 2017 23:09:14 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 2 Jun 2017 23:09:14 +0000 (UTC) To: Drew Adams , Dmitry Gutov , 27193@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Jun 03 01:09:09 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dGvgq-0007xQ-SY for geb-bug-gnu-emacs@m.gmane.org; Sat, 03 Jun 2017 01:09:09 +0200 Original-Received: from localhost ([::1]:51763 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dGvgw-0001kG-1O for geb-bug-gnu-emacs@m.gmane.org; Fri, 02 Jun 2017 19:09:14 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38759) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dGvgn-0001ji-J5 for bug-gnu-emacs@gnu.org; Fri, 02 Jun 2017 19:09:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dGvgk-0008I2-Do for bug-gnu-emacs@gnu.org; Fri, 02 Jun 2017 19:09:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:49413) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dGvgk-0008Hu-8a for bug-gnu-emacs@gnu.org; Fri, 02 Jun 2017 19:09:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dGvgk-00056B-46 for bug-gnu-emacs@gnu.org; Fri, 02 Jun 2017 19:09:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Ryan Thompson Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 02 Jun 2017 23:09:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 27193 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 27193-submit@debbugs.gnu.org id=B27193.149644493619588 (code B ref 27193); Fri, 02 Jun 2017 23:09:02 +0000 Original-Received: (at 27193) by debbugs.gnu.org; 2 Jun 2017 23:08:56 +0000 Original-Received: from localhost ([127.0.0.1]:52090 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dGvge-00055s-Kc for submit@debbugs.gnu.org; Fri, 02 Jun 2017 19:08:56 -0400 Original-Received: from mail-it0-f46.google.com ([209.85.214.46]:38162) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dGvgd-00055f-85 for 27193@debbugs.gnu.org; Fri, 02 Jun 2017 19:08:55 -0400 Original-Received: by mail-it0-f46.google.com with SMTP id r63so33261496itc.1 for <27193@debbugs.gnu.org>; Fri, 02 Jun 2017 16:08:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thompsonclan-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=+hBqJjPD2w2U2HL9yWIUn6lXOnK1NsXjVCFOJglexy8=; b=Y+U94ifR64S5woz51M0vNFHUlApXs+HbcZlVPtlKaZ5VceCIGhq29fByrScBDP33VT KFCvlfGA4lu/sfC9RaF/cdyRniGJpgKCKS1ofQsotSPF3xtFS5YYLSShWzmtQEeE4/c3 ypML0XD9Q0Y7h3yHSoka9XYW27g1Lu6NfpeVQueHcGVTVxgTpXaSAS0UsSYyhY8hr8zG N1bJzTE8iBIpeKEl5E8tUD9JGBUBkzWUqmsszx5GWT0hXbLFOOrnOP6IH9Ymc4s60X+i rNxxZB+wRlFn4YRKzq4pcYZuqOxfc5MFrCTshRRtNaibPLENe6PdOm69f2HdZxuNlQLg G4aw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=+hBqJjPD2w2U2HL9yWIUn6lXOnK1NsXjVCFOJglexy8=; b=Msc8uOiUGIuskhk46i1GPaRdiduhPa//YwKNb8K9l0vjc3G7bSZYHx+HZ0rrUVbaa0 Xzx3vkhp1ZChpr7WwwWbInBImKlZ2+BA2Gtq7e1ketXUNWiugZ/dtknyC6Lvi16qlPmA KQbZPo4VHpb77His5c4Cd2YNlj2rQSHbelSzdGYwSJ14Uq3i/Zh5X3wIMkhOL61QvuuM GHahs5uubrx8gIjMvqi5dspC0oNhRfhmJ6z7ytS1AdsDAwnlNXBGUQUOPNWgICMUf69O G0uc0tH+a7zi+qUvXvj54+XcO1b9w8d+a4nmL0S2n0LtSnKRWMx1YYFM28lp1rDG1Z6b R6iQ== X-Gm-Message-State: AODbwcDziPxkLWzHjqAgGx4/zGmeceAr1vmGqNZJoGJx4lQ1fMt5G7/0 sFrMTKLy8DSktFX0fUBrgV5jWooflvOl X-Received: by 10.36.54.210 with SMTP id l201mr1950845itl.65.1496444929669; Fri, 02 Jun 2017 16:08:49 -0700 (PDT) In-Reply-To: <236c968a-a11f-4a5a-88bc-f60edb50aa18@default> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:133188 Archived-At: --001a1144046875ab1a0551023ca9 Content-Type: text/plain; charset="UTF-8" On Fri, Jun 2, 2017 at 6:19 PM Drew Adams 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. --001a1144046875ab1a0551023ca9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri= , Jun 2, 2017 at 6:19 PM Drew Adams <drew.adams@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 actua= lly done in the past, but currently does not), because by calling ido-compl= eting-read the code has already specified it wants ido completion. Similarl= y, tmm is implementing a very different behavior from completing-read that = is only recognizable as regular completion if you specifically go looking f= or leaks in the abstraction, and for the same reason I don't think tmm = should be paying attention to completing-read-function.
--001a1144046875ab1a0551023ca9--