From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: a bug rendering ido unusable Date: Tue, 29 Apr 2008 23:22:56 -0400 Message-ID: References: <200804292005.08722.pogonyshev@gmx.net> <87ej8ofj3g.fsf@kfs-lx.rd.rdm> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1209525791 18901 80.91.229.12 (30 Apr 2008 03:23:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 30 Apr 2008 03:23:11 +0000 (UTC) Cc: emacs-devel@gnu.org, Paul Pogonyshev To: storm@cua.dk (Kim F. Storm) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Apr 30 05:23:47 2008 connect(): Connection refused Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Jr2v5-0006Ra-9g for ged-emacs-devel@m.gmane.org; Wed, 30 Apr 2008 05:23:47 +0200 Original-Received: from localhost ([127.0.0.1]:32793 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jr2uO-0003DH-9V for ged-emacs-devel@m.gmane.org; Tue, 29 Apr 2008 23:23:04 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jr2uJ-0003Cv-H3 for emacs-devel@gnu.org; Tue, 29 Apr 2008 23:22:59 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jr2uI-0003CR-6m for emacs-devel@gnu.org; Tue, 29 Apr 2008 23:22:59 -0400 Original-Received: from [199.232.76.173] (port=37729 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jr2uI-0003CN-2O for emacs-devel@gnu.org; Tue, 29 Apr 2008 23:22:58 -0400 Original-Received: from ironport2-out.pppoe.ca ([206.248.154.182] helo=ironport2-out.teksavvy.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Jr2uH-0007PD-Oo for emacs-devel@gnu.org; Tue, 29 Apr 2008 23:22:57 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgoEAD+CF0jO+JghdGdsb2JhbACBU499ASebKg X-IronPort-AV: E=Sophos;i="4.25,725,1199682000"; d="scan'208";a="19619617" Original-Received: from smtp.pppoe.ca (HELO smtp.teksavvy.com) ([65.39.196.238]) by ironport2-out.teksavvy.com with ESMTP; 29 Apr 2008 23:22:56 -0400 Original-Received: from pastel.home ([206.248.152.33]) by smtp.teksavvy.com (Internet Mail Server v1.0) with ESMTP id KHA88256; Tue, 29 Apr 2008 23:22:56 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 746E581E8; Tue, 29 Apr 2008 23:22:56 -0400 (EDT) In-Reply-To: <87ej8ofj3g.fsf@kfs-lx.rd.rdm> (Kim F. Storm's message of "Tue, 29 Apr 2008 23:26:43 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:96184 Archived-At: >> Hi, >> >> I have recompiled Emacs from CVS today and found that ido no longer >> differentiates between files and directories. E.g. when I type >> '~/ema RET' it opens directory '~/emacs' in dired mode, instead of >> navigating into it inside the minibuffer. It must be a bug since >> I don't see how that is anywhere near useful. >> >> OTOH, there doesn't seem to be any recent modifications of ido, so >> this might be a problem in some other place, e.g. in a function >> that does is-this-a-directory check. >> >> This is on GNU/Linux, could matter. 'emacs -q' shows the same >> behavior after 'M-x ido-mode'. > There has been a lot of changes to the basic completion stuff - maybe > some of those changes broke ido. Yes, that's the most likely explanation. > I don't have time to look into it at this time - so if someone else > could take a look I'd appreciate it. > Stefan, do you know what might have happened ?? The handling of completion predicate together with read-file-name-internal has changed and I think it's the most likely culprit. I haven't had time to look into it yet, tho, Stefan