From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.bugs Subject: bug#49761: file-cache-minibuffer-complete has become unusable for duplicate file names in MacOSX 27.x emacs Date: Fri, 30 Jul 2021 20:58:55 +0300 Organization: LINKOV.NET Message-ID: <87lf5nisyo.fsf@mail.linkov.net> References: <87o8alvwby.fsf@mail.linkov.net> <83bl6lrnrh.fsf@gnu.org> <878s1pvunb.fsf@mail.linkov.net> <838s1osyv1.fsf@gnu.org> <87y29ovrgj.fsf@mail.linkov.net> <87v94su45t.fsf@mail.linkov.net> <8335rws641.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27328"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (x86_64-pc-linux-gnu) Cc: aaron@brightbytes.net, 49761@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jul 30 20:05:18 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m9Wso-0006uX-BF for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 30 Jul 2021 20:05:18 +0200 Original-Received: from localhost ([::1]:60498 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m9Wsn-0006f4-Cc for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 30 Jul 2021 14:05:17 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55122) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m9Wra-0004hm-Dk for bug-gnu-emacs@gnu.org; Fri, 30 Jul 2021 14:04:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:49312) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1m9Wra-0002ll-4t for bug-gnu-emacs@gnu.org; Fri, 30 Jul 2021 14:04:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1m9WrZ-0002w9-U2 for bug-gnu-emacs@gnu.org; Fri, 30 Jul 2021 14:04:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Juri Linkov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 30 Jul 2021 18:04:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 49761 X-GNU-PR-Package: emacs Original-Received: via spool by 49761-submit@debbugs.gnu.org id=B49761.162766821911261 (code B ref 49761); Fri, 30 Jul 2021 18:04:01 +0000 Original-Received: (at 49761) by debbugs.gnu.org; 30 Jul 2021 18:03:39 +0000 Original-Received: from localhost ([127.0.0.1]:60858 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1m9WrD-0002vZ-EZ for submit@debbugs.gnu.org; Fri, 30 Jul 2021 14:03:39 -0400 Original-Received: from relay3-d.mail.gandi.net ([217.70.183.195]:38605) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1m9WrC-0002vJ-DU for 49761@debbugs.gnu.org; Fri, 30 Jul 2021 14:03:38 -0400 Original-Received: (Authenticated sender: juri@linkov.net) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id D5B7C60008; Fri, 30 Jul 2021 18:03:30 +0000 (UTC) In-Reply-To: <8335rws641.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 30 Jul 2021 08:50:06 +0300") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:210924 Archived-At: >> 4. 'make C-TAB' then the completions buffer is displayed and the cursor >> jumps to the beginning because there are completions that don't begin >> with the same prefix "make" such as flymake.el, pmake.el, ob-makefile.el. > > Is this reasonable behavior? It seems to try second-guessing what the > user will do next, but that guess is not necessarily correct. I don't know, this is the default behavior for completions that don't share a common prefix.