From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.bugs Subject: bug#60411: 29.0.60; minibuffer-next-completion skips first candidate when completions-header-format and completion-show-help are nil Date: Sun, 01 Jan 2023 17:05:18 +0000 Message-ID: <226b32f79f7db2be1bbe@heytings.org> References: <87zgb5lx6y.fsf@oracle.com> <6c9d91cffcdbff97f034@heytings.org> <87lemot7ek.fsf@gmail.com> <0a62cbaeff1ee0497715@heytings.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33148"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Knut Anders Hatlen , 60411@debbugs.gnu.org To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Jan 01 18:06:26 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 1pC1my-0008MG-8x for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 01 Jan 2023 18:06:24 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pC1me-0001Lm-SP; Sun, 01 Jan 2023 12:06: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 1pC1mc-0001LQ-Ok for bug-gnu-emacs@gnu.org; Sun, 01 Jan 2023 12:06:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pC1mc-0003Ju-9I for bug-gnu-emacs@gnu.org; Sun, 01 Jan 2023 12:06:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pC1mc-0003M8-59 for bug-gnu-emacs@gnu.org; Sun, 01 Jan 2023 12:06:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 01 Jan 2023 17:06:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 60411 X-GNU-PR-Package: emacs Original-Received: via spool by 60411-submit@debbugs.gnu.org id=B60411.167259272112847 (code B ref 60411); Sun, 01 Jan 2023 17:06:02 +0000 Original-Received: (at 60411) by debbugs.gnu.org; 1 Jan 2023 17:05:21 +0000 Original-Received: from localhost ([127.0.0.1]:41615 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pC1lx-0003L8-26 for submit@debbugs.gnu.org; Sun, 01 Jan 2023 12:05:21 -0500 Original-Received: from heytings.org ([95.142.160.155]:54590) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pC1lv-0003Kx-TQ for 60411@debbugs.gnu.org; Sun, 01 Jan 2023 12:05:20 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1672592718; bh=m/Tfr8+bmlIyfSBg/9zuZfjwRgVL+TKIlCep5rPF5lM=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=MRuMXKR+yHL8GSEK3BR/UTd80cD0vbS6/Ue0sQL5xZYaqTVOwUDf1PxThSNWMohWk HdXgWOQtvcZYOJX5h+oiKhI6GmziOkxFafNzNiGkXfmDXdNfMvAKrPbpfL+J2OoO54 Xodj8tkFOf7GiFK/nnotBXmh235aMuSco9lMLnkzImPYdD729+LIalneENJJyBqrxp SzB2KX60hZVs8y2I0a2sIfTr10uileOYBg5gzfCARL7+/Fo2dSoZiReE8lsSNR2xuB CJ1gXAsKnil7w2npg31ON69gOU74RAXV/1AS3RXdEg0BrDblrhAHi5bjx6qZZ0/jGA Xv6oJXMNxxMoA== In-Reply-To: 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:252254 Archived-At: > > Yuck. I get the impression that it would be cleaner to fix "the first > call to `minibuffer-next-completion`" instead. > That was my impression, too. Until I tried to fix "the first call to `minibuffer-next-completion`". But I may have missed something, of course.