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#67661: 30.0.50; *Completions* has started popping up for icomplete-in-buffer Date: Sat, 09 Dec 2023 16:40:48 +0200 Message-ID: <83y1e3wia7.fsf@gnu.org> References: <87o7f3e4cb.fsf@melete.silentflame.com> <83wmtr2mye.fsf@gnu.org> <87lea3wpai.fsf@zephyr.silentflame.com> <8334wby0bq.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7290"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 67661@debbugs.gnu.org, juri@linkov.net, 67001@debbugs.gnu.org, spwhitton@spwhitton.name To: Eshel Yaron Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Dec 09 15:42:07 2023 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 1rByWs-0001hv-SD for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 09 Dec 2023 15:42:07 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rByWb-0005A7-AF; Sat, 09 Dec 2023 09:41:50 -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 1rByWa-00059z-Qx for bug-gnu-emacs@gnu.org; Sat, 09 Dec 2023 09:41:48 -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 1rByWa-0005y9-Im for bug-gnu-emacs@gnu.org; Sat, 09 Dec 2023 09:41:48 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rByWo-0001ZH-53 for bug-gnu-emacs@gnu.org; Sat, 09 Dec 2023 09:42: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, 09 Dec 2023 14:42:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 67661 X-GNU-PR-Package: emacs Original-Received: via spool by 67661-submit@debbugs.gnu.org id=B67661.17021328865961 (code B ref 67661); Sat, 09 Dec 2023 14:42:02 +0000 Original-Received: (at 67661) by debbugs.gnu.org; 9 Dec 2023 14:41:26 +0000 Original-Received: from localhost ([127.0.0.1]:47070 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rByWD-0001Xw-QB for submit@debbugs.gnu.org; Sat, 09 Dec 2023 09:41:26 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56566) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rByWB-0001Wj-DG; Sat, 09 Dec 2023 09:41:24 -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 1rByVr-0005ud-Q4; Sat, 09 Dec 2023 09:41:03 -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=QMHVVBuE7sTnQog+brYPpZN3VCsLqrLl0CoeL5VKnUc=; b=pJdhimHnfQMo Oicc8T/1ZwrOU+Fob2lww68pX0LaklzNkjz6dZahEawgVG2Z5s4yJzuFZ7drtZV8AKjz9ZqS8O3+4 1h76usIPPat9rkx0zb80LlUSs0FoACVtdDOa8abdjNt7wo9Bv2D5qf9fRhrui6kydpPUjZ3TgULnO ZzsTPQZe8ruEPF0nvLS6OcM1UsZiMoSkWAZm8KC0qBgQqIFeYB8yqtLHCQP5UMoSTRLci1rnBS2Rv D97m6Tmfm1yF1M5d1MOkjzqOK/XtY3YfpRecedJq1qvSk6b7KTz6uZE4xQIg2bKmkFS5g1bZDViFT Go9A3qi8dJJFk77RmGRbCw==; In-Reply-To: (message from Eshel Yaron on Sat, 09 Dec 2023 15:13:53 +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:275858 Archived-At: > From: Eshel Yaron > Cc: spwhitton@spwhitton.name, juri@linkov.net, 67661@debbugs.gnu.org, > 67001@debbugs.gnu.org > Date: Sat, 09 Dec 2023 15:13:53 +0100 > > Eli Zaretskii writes: > > > Once again, the fact that the second TAB shows both completion > > interfaces is not the problem: as you point out that was how Emacs > > behaved since long ago. The problem here is that the _first_ TAB does > > NOT show in-buffer completions. > > Yes, but what I pointed out was that the first TAB has been showing both > interfaces since Emacs 27, just not with this particular recipe. That's not what I see in Emacs 29. There' the first TAB shows only the in-buffer completions, and the second TAB pops up the *Completions* buffer (without removing the in-buffer completions). > >> If it doesn't make sense for `icomplete-in-buffer` to appear along > >> with the *Completions* buffer > > > > Again, this is not the problem to solve. > > Could you explain what you mean here? If this behavior doesn't make > sense, isn't it worth trying to solve it for all cases, rather than just > for one specific case? I don't think I understand what you mean by "one specific case". Which case, and why is it specific? Sean reported a regression in behavior under icomplete-in-buffer, so I looked into the recipe he posted. What I saw was that Emacs 29 shows the in-buffer completions after the first TAB and adds to that the *Completions* buffer after the second TAB. By contrast, Emacs 30 shows nothing after the first TAB, and shows both in-buffer completions and the *Completions* buffer after the second TAB. So my conclusion was that the regression is the behavior after the first TAB. If this conclusion is incorrect, please tell what did I miss.