From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#74617: 30.0.92; ffap-menu always displays the *Completions* buffer Date: Sat, 30 Nov 2024 11:28:13 +0200 Message-ID: <86frn99iky.fsf@gnu.org> References: <87r06turur.fsf@daniel-mendler.de> <86ser99lrd.fsf@gnu.org> <875xo5unlo.fsf@daniel-mendler.de> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9240"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 74617@debbugs.gnu.org, monnier@iro.umontreal.ca To: Daniel Mendler Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Nov 30 10:29:38 2024 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 1tHJnG-0002Gh-Gx for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 30 Nov 2024 10:29:38 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tHJmi-0004IP-RU; Sat, 30 Nov 2024 04:29:04 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tHJmg-0004IG-Pd for bug-gnu-emacs@gnu.org; Sat, 30 Nov 2024 04:29:02 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1tHJmg-00067T-7y for bug-gnu-emacs@gnu.org; Sat, 30 Nov 2024 04:29:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debbugs.gnu.org; s=debbugs-gnu-org; h=References:In-Reply-To:From:Date:To:Subject; bh=Wj5R2RmS8rLD95JNyazru2BXfhGhsclfnJU3led3fOg=; b=vIwiyK2t+0wHdCEYcVUhNLwgzv21EOi3J1WDlwkvVbflaHm9L05bp+/HXdwIG+7fOQ6r3XHD8Lbs6TNyIAOGlXLCGZ3PlFcZ2xPHErTYNBHjRUK6Lc0/C8quiCJtn6umHe7soK/nZ+lkFx0UjU45JYhSWlbbWKN4mgYU4+JUJBDpbuyg0EKviBE60G56kSSMjPerSQDid6VBUfwitbm2fVRdgZlCHHg0UvEa8P1ywc9E8mJ3oYzhugeq9oB5MaA3dMI4PjTvJ1aY+JUE7MDDW4kzK4hJfToEAuWiH4yHfi5UDB4ESFI/0Jc7s8rJur6j67uaxOC5Pt+TEGFy0Y/kFA==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1tHJmf-0005K6-Uf for bug-gnu-emacs@gnu.org; Sat, 30 Nov 2024 04:29:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 30 Nov 2024 09:29:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 74617 X-GNU-PR-Package: emacs Original-Received: via spool by 74617-submit@debbugs.gnu.org id=B74617.173295890520389 (code B ref 74617); Sat, 30 Nov 2024 09:29:01 +0000 Original-Received: (at 74617) by debbugs.gnu.org; 30 Nov 2024 09:28:25 +0000 Original-Received: from localhost ([127.0.0.1]:45406 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tHJm4-0005Im-Qd for submit@debbugs.gnu.org; Sat, 30 Nov 2024 04:28:25 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:55738) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tHJm2-0005IY-SO for 74617@debbugs.gnu.org; Sat, 30 Nov 2024 04:28:23 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tHJlw-0005yu-Hm; Sat, 30 Nov 2024 04:28:16 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=Wj5R2RmS8rLD95JNyazru2BXfhGhsclfnJU3led3fOg=; b=hsF3OWJipGWi SQB4mbZrC+H0SSCQ0HBBQXTkzokdBniAxe3XLj/eOjVIJUKZ6+QO2COM2KfO4QD2ACifDlBU803Ed sdFP3h70zvtBmgKm4bZRBU4NBXWOXIAH4/aCK+hWR/G10YalxXAmczJhFLcWWVU1LIR9aJnKB8cmX 1Si4viXw+yz6N/2mu6cZ6k6NtBEgEe17/kYSXGFWk0Js0gpTIkEQClDPnmJ24DVRC+reaZZVxnrUH pb13QB4bXqhG323NhrQMK/qWKpvf2qlcpzXxIuLMxg9d+4WgXfg4XS/0LhovvTyvs6656hfoz+IhI YaW5jWV/2TM6zW/hHxfjgA==; In-Reply-To: <875xo5unlo.fsf@daniel-mendler.de> (message from Daniel Mendler on Sat, 30 Nov 2024 09:34:11 +0100) 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:296121 Archived-At: > From: Daniel Mendler > Cc: 74617@debbugs.gnu.org, monnier@iro.umontreal.ca > Date: Sat, 30 Nov 2024 09:34:11 +0100 > > Eli Zaretskii writes: > > > emacs -Q > > M-x icomplete-mode RET > > C-x C-f nt/INSTALL.W64 RET > > M-x ffap-menu RET > > > > I see only the *Completions* buffer, no other display of the > > candidates. What did I miss? > > Oh, right. I missed that. I think the problem here is that Icomplete > uses a delay (`icomplete-compute-delay'). Other completion UIs don't > have such a delay and show the candidates immediately. This makes the > problem a little more difficult, in particular with respect to auto > detection. Alternatively, we could consider the cases where more than one completion list is shown a bug in the mode which shows the completions even though the application already did. IOW, instead of considering this a problem of the command the user invokes, consider this a bug in the non-default completion UI currently in effect. It is basically a flaw in the design of those completion UIs. > Another alternative to auto detection could be that the completion table > communicates to `completing-read' via metadata that immediate candidate > display is desired. The completion UI could then act accordingly. > Default completion would call `minibuffer-completion-help' and Icomplete > could update immediately, ignoring `icomplete-compute-delay'. This sounds too indirect to me, it could cause unintended adverse consequences, especially in nested scenarios. There's a simpler alternative: we could say we don't care, as long as only a few alternative UIs have this issue. It isn't a catastrophe.