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 14:30:32 +0200 Message-ID: <86v7w47vkn.fsf@gnu.org> References: <87r06turur.fsf@daniel-mendler.de> <86ser99lrd.fsf@gnu.org> <875xo5unlo.fsf@daniel-mendler.de> <86frn99iky.fsf@gnu.org> <8734j9ukju.fsf@daniel-mendler.de> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22524"; 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 13:33:23 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 1tHMf4-0005er-U1 for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 30 Nov 2024 13:33:23 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tHMeq-0000Sj-Iu; Sat, 30 Nov 2024 07:33:08 -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 1tHMen-0000SO-Gj for bug-gnu-emacs@gnu.org; Sat, 30 Nov 2024 07:33:06 -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 1tHMek-0001mZ-Gf for bug-gnu-emacs@gnu.org; Sat, 30 Nov 2024 07:33:03 -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=2wgSxCcRCRa2xOAWRBvpNwAL3FdZg217eHiFgURmlSg=; b=UV6emTGVSFzfzsDh7omYIrY7VnN6gtS0TwyeQjuoUC/cbO2EdXSrnu4b5b4fesxT+47PZLlBrjf7d3UYF8PXOfOsPFJptvYSvPiWxVPzK6LhJJhMdIAIrvrg7g9sGufwG7y1juR1dh3yrVlsBE3P7yE6hg8YRF3w4x7VSRIfNG6qZ3N/zBIzBs/quzpxdPuBbd2aybY67gJBCxkrQcFLVmi5C5nWyBBm3y+Af0SomCQ1Dl57skrAJ8zrSH+U3xuYs8AVBxn/ZPjHpuGqojyzX9ibnsezrNbXIbMbth6DpG0WAbMhKk9psP31vhHnf6eAPBsm4UHp41UFbQ63eb+5pw==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1tHMek-0006eR-AY for bug-gnu-emacs@gnu.org; Sat, 30 Nov 2024 07:33:02 -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 12:33:02 +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.173296998025557 (code B ref 74617); Sat, 30 Nov 2024 12:33:02 +0000 Original-Received: (at 74617) by debbugs.gnu.org; 30 Nov 2024 12:33:00 +0000 Original-Received: from localhost ([127.0.0.1]:45867 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tHMeh-0006e9-Fb for submit@debbugs.gnu.org; Sat, 30 Nov 2024 07:32:59 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:43394) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tHMef-0006ds-7c for 74617@debbugs.gnu.org; Sat, 30 Nov 2024 07:32:57 -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 1tHMcS-00014S-G9; Sat, 30 Nov 2024 07:30:40 -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=2wgSxCcRCRa2xOAWRBvpNwAL3FdZg217eHiFgURmlSg=; b=mLm5BhrsKMsj wgTMFGgBPRsndgl4ThShxeqcyEev8TkNWdS3sTvO4qMB04+ibniKON2gljUzGUHY1xXTINet+CPco AEZqQTWHTe9ba3PkXHxZCVHWaOe7BIvnpQCu61LFbWv9mVTPZPHIm0JQv2Dm6SUYf9MDkQkgISlYG T1dS3V4tqLHTzxKiWljCYodkBS8bVd7sKazlS+LVTQSW1zNxUQwpLO6ISIOAOTj7RKQQZmvMn5bgd zDxpra0tTwwuubsn1VNLUvqm9yN/1Vr8+ShZ2T2twbq3w44+Wza+2borEZuvDLIDOGEoVxW8AtKbE k+4Nl4EjCllcw+vAOFJT6w==; In-Reply-To: <8734j9ukju.fsf@daniel-mendler.de> (message from Daniel Mendler on Sat, 30 Nov 2024 10:40:05 +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:296163 Archived-At: > From: Daniel Mendler > Cc: 74617@debbugs.gnu.org, monnier@iro.umontreal.ca > Date: Sat, 30 Nov 2024 10:40:05 +0100 > > Eli Zaretskii writes: > > 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. > > I see it differently. The problem is in the tmm and ffap commands which > lead to a mixture of completion UIs. Even if another completion UI is in > effect, the default completion UI is called by tmm and ffap, bypassing > the `completing-read' abstraction. I don't understand: ffap-menu calls completing-read, so what abstraction does it bypass, and how? > It is not the responsibility of > alternative completion UIs to work around this. Work around what? > Mixing multiple > completion UIs is not ideal since it will lead to an incoherent UI and > also to conflicts in how the user interacts with the minibuffer. The question is: who should pay attention and understand that "the other" completion is being called? > >> 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. > > By using the completion metadata as part of the completion table, the > effect on nested scenarios is explicitly avoided. Problems with nesting > only occur if a variable is let-bound around `completing-read'. You assume that the completion table is never passed to inner levels? Is that assumption solid?