Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Newsgroups: gnu.emacs.bug Subject: bug#43120: 28.0.50; fido-mode: M-j before completions appear selects wrong choice Date: Thu, 03 Sep 2020 13:40:28 +0100 Lines: 36 Sender: "Debbugs-submit" Approved: bug-gnu-emacs@gnu.org Message-ID: References: <8736433l4c.fsf@iris.silentflame.com> <87zh6bhex9.fsf@gmail.com> <87sgc1d1kl.fsf@gnus.org> <87v9gxpd22.fsf@gmail.com> <87d033owxv.fsf@gmail.com> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: usenet.stanford.edu 1599136864 13192 209.51.188.17 (3 Sep 2020 12:41:04 GMT) X-Complaints-To: action@cs.stanford.edu Cc: 43120@debbugs.gnu.org, Sean Whitton To: Lars Ingebrigtsen Envelope-to: bug-gnu-emacs@gnu.org X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 03 Sep 2020 12:41:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 43120 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-transfer-encoding; bh=QYzmvR+LOS0g0qlHBJB/kH2xNNcGsFB1jKC14z749r8=; b=N+2/NMJAtgerLyA2cfv79JwcHs+aZYhh/cgZYezEVxodyWcvzDD46YZRX5epphI/M6 WkoTkW2b5RbBbKqwhjF5laBD68BUPSsSCiv2rXsSlHtL9dZcit+XMkDu7YxXm6NII9Fn bBGVivfot7liOwMbd7luCcdleKYX7B4/9mRvLOw8hCYtsCIXmsT1CRm7du9Zctswthxh Y2aoTXdtTVMdTAFjQmh1hdGjsqTFpkJCCePpmc8bqeQL+IHayaplxHIWY/34v3ATVmTM YzLZWLrfiyrOLx+h81Dnk+52YFhTZ9QOIcYIlCb0WH4ebWO7yarGbF7OzriSDHxDO/a9 YzkA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-transfer-encoding; bh=QYzmvR+LOS0g0qlHBJB/kH2xNNcGsFB1jKC14z749r8=; b=bxJIpGpZ2LmZUkv+HfACvep0dRlEIgSX84O99OJ/GiufMycxwyFBM38b1eYXs98RdH IOpwc2mSwgmaJtGWacfNoK4qGU+BkXYWUQKQqD6wJquRQWXQ+uGvMzTXwAUsRknusON4 8fKzD1LN3BEVfxPDs2A5UxlPyScVI+KRWt9CSAvLFLrZV4f3ti4U6fkdMV4/ycTGSOZo YMTeJQ4yVB2TweVmz6kU7kJCRx8KLOODtABMsjgAYW5wPxdUba39Vl4WTJOC2bmUQ+Pj fs5xm7HrgyubrncYDmtQ7nnqdHNZm0yt5Vlb01LbUQ5BLoUsO6qa2oulRrpknxxit5hz amUg== X-Gm-Message-State: AOAM530b0skYECpcc4hCdGmGbybfNveNYdrkA5wZOn0JDBvMJDhOMv/h saZlf4QTK0JUUmKt0/VuNHtVHJMvAF8= X-Google-Smtp-Source: ABdhPJyEAAPwyhPVYF68W5o96CASH2AIzEnxi1gRwCDsvod/bkxLQ6cqOAVhjz1cmA1YY5alo6wRAw== X-Received: by 2002:adf:a48d:: with SMTP id g13mr2265349wrb.212.1599136829910; Thu, 03 Sep 2020 05:40:29 -0700 (PDT) In-Reply-To: <87v9gxpd22.fsf@gmail.com> ("=?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?="'s message of "Tue, 01 Sep 2020 19:27:49 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) X-Spam-Score: 0.0 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list Errors-To: debbugs-submit-bounces@debbugs.gnu.org X-Spam-Score: -1.0 (-) 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: , X-Mailman-Original-Message-ID: <87d033owxv.fsf@gmail.com> X-Mailman-Original-References: <8736433l4c.fsf@iris.silentflame.com> <87zh6bhex9.fsf@gmail.com> <87sgc1d1kl.fsf@gnus.org> <87v9gxpd22.fsf@gmail.com> Xref: csiph.com gnu.emacs.bug:134825 Jo=C3=A3o T=C3=A1vora writes: > I see in the side thread there seems to be a straightforward and logical > fix. If that makes sense globally and also fixes it for Sean, I'm fine > with it, otherwise I'd suggest having a second look at the original > problem that prompted the problematic patch, specifically at why > fido-mode didn't suffer from it. It didn't, but it sure does now. I just noticed that this affects bare-bones fido-mode as well, i.e. even without using M-j we get some akward and very highly annoying cache. In an Emacs -Q with fido-mode enabled: (bound-and-true-p [press C-h f RET here, slowly]) now move the point to the "setq" in, say (setq blabla ) And type C-h f RET here, quickly. You'll be presented with `bound-and-true-p`'s doc, not `setq`'s. This is a regression: the bug should be fixed ASAP. Maybe some "clearing" as was suggested is in order. I'm not very confortable writing that patch right now. Can anyone else do it? Or should we revert the original fix instead in the meantime? Jo=C3=A3o