From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.bugs Subject: bug#15980: 24.3.50; `minibuffer-complete-word': case where it does not work correctly Date: Tue, 7 Jan 2014 09:50:17 -0800 (PST) Message-ID: <15a33bcc-ce90-484c-bb32-64d05647a09d@default> References: <20db5440-5f90-46d1-b0a2-25f495661ae6@default> <87d2k4hu77.fsf@bzg.ath.cx> <87d76d4c-4684-43de-876e-46ebbdcb4b3e@default> <87fvozg1ep.fsf@bzg.ath.cx> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1389117081 24238 80.91.229.3 (7 Jan 2014 17:51:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 7 Jan 2014 17:51:21 +0000 (UTC) Cc: 15980@debbugs.gnu.org To: Bastien Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Jan 07 18:51:25 2014 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1W0aoG-0004VN-1i for geb-bug-gnu-emacs@m.gmane.org; Tue, 07 Jan 2014 18:51:24 +0100 Original-Received: from localhost ([::1]:42102 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W0aoF-0005fg-Ll for geb-bug-gnu-emacs@m.gmane.org; Tue, 07 Jan 2014 12:51:23 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57939) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W0ao4-0005f9-Te for bug-gnu-emacs@gnu.org; Tue, 07 Jan 2014 12:51:21 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W0anv-0003Mv-0g for bug-gnu-emacs@gnu.org; Tue, 07 Jan 2014 12:51:12 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:55546) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W0anu-0003Mr-TB for bug-gnu-emacs@gnu.org; Tue, 07 Jan 2014 12:51:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1W0anu-0004Aj-HP for bug-gnu-emacs@gnu.org; Tue, 07 Jan 2014 12:51:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Drew Adams Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 07 Jan 2014 17:51:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 15980 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 15980-submit@debbugs.gnu.org id=B15980.138911702615984 (code B ref 15980); Tue, 07 Jan 2014 17:51:02 +0000 Original-Received: (at 15980) by debbugs.gnu.org; 7 Jan 2014 17:50:26 +0000 Original-Received: from localhost ([127.0.0.1]:41331 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1W0anJ-00049j-Tp for submit@debbugs.gnu.org; Tue, 07 Jan 2014 12:50:26 -0500 Original-Received: from userp1040.oracle.com ([156.151.31.81]:21995) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1W0anG-00049Y-Lv for 15980@debbugs.gnu.org; Tue, 07 Jan 2014 12:50:23 -0500 Original-Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id s07HoJnp026039 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Jan 2014 17:50:19 GMT Original-Received: from aserz7021.oracle.com (aserz7021.oracle.com [141.146.126.230]) by ucsinet22.oracle.com (8.14.5+Sun/8.14.5) with ESMTP id s07HoI8O026139 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Jan 2014 17:50:19 GMT Original-Received: from abhmp0014.oracle.com (abhmp0014.oracle.com [141.146.116.20]) by aserz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s07HoIbP014950; Tue, 7 Jan 2014 17:50:18 GMT In-Reply-To: <87fvozg1ep.fsf@bzg.ath.cx> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.8 (707110) [OL 12.0.6680.5000 (x86)] X-Source-IP: ucsinet22.oracle.com [156.151.31.94] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.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-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:83127 Archived-At: > >> See the first comment in `completion--try-word-completion': > >> the function considers that either a space *or* an hyphen will > >> be used to separate words. The "or" is exclusive. > > > > `completion--try-word-completion' is an *implementation*. If > > that's what it does then it does not do what the doc says, right? > > So either the doc needs to be fixed to fit the implementation or > > vice versa, no? >=20 > `completion--try-word-completion' does not have a docstring. I meant the doc I cited earlier. It's not about whether that function's behavior matches its code comment. It's about whether Emacs behavior matches what we tell users that behavior is. > > Are you saying that because those completion candidates contain > > space chars? There are *lot* of places where Emacs can use > > completion for candidates that contain space chars. >=20 > My point is that there is little chance that *many* non-contrived > strings can be completed either as xxx- or as xxx\ (wich a space.) OK. > > `completing-read' is completely general. Emacs should make no > > assumptions about whether completion candidates happen to contain > > spaces. >=20 > Agreed. I couldn't find a fix. Then perhaps leave it open until someone can. One possible fix is to document the actual behavior instead of saying what we say now. > >> I'm for closing this bug until it really hit someone. > > > > That's not right. The product and the doc do not agree, as you > > have pointed out. That alone is a bug. One way or another it > > should be fixed. >=20 > So let's keep this open and find someone that can fix it properly. OK. But again, if you can describe the actual behavior, perhaps it is enough to correct what we say currently.