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.devel Subject: Re: Select completions from the minibuffer Date: Tue, 22 Mar 2022 16:49:59 +0200 Message-ID: <831qyuf3e0.fsf@gnu.org> References: <86k0d06dik.fsf@mail.linkov.net> <87ee3714li.fsf@gnus.org> <86r1773sb4.fsf@mail.linkov.net> <87pmmquew4.fsf@gnus.org> <86h7817mj4.fsf@mail.linkov.net> <87ilsgx5fx.fsf@gnus.org> <86bkxz3y1h.fsf@mail.linkov.net> <875yo7p0hh.fsf@gnus.org> <86v8w675un.fsf@mail.linkov.net> <837d8mf6pf.fsf@gnu.org> <20220322141815.2iq7jec2d5lvfox3@Ergus> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25766"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, emacs-devel@gnu.org, juri@linkov.net To: Ergus Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Mar 22 15:51:56 2022 Return-path: Envelope-to: ged-emacs-devel@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 1nWfrW-0006S5-Oi for ged-emacs-devel@m.gmane-mx.org; Tue, 22 Mar 2022 15:51:54 +0100 Original-Received: from localhost ([::1]:53556 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nWfrV-0003x2-BD for ged-emacs-devel@m.gmane-mx.org; Tue, 22 Mar 2022 10:51:53 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:53410) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nWfqE-0002TX-17 for emacs-devel@gnu.org; Tue, 22 Mar 2022 10:50:36 -0400 Original-Received: from [2001:470:142:3::e] (port=38938 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nWfq9-00010t-7q; Tue, 22 Mar 2022 10:50:33 -0400 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=cnlN3Z9pMtgBrmMLwoUU4b+h5tIIUN5IRBdPH0WEOPQ=; b=PLIBpK1oACj8 q9x5LkDSqOLsL/91s+2O5MvmNUv0VXUKtMJOafunOjFJBdZcUaXsTxWH3hGPUyjlXZHP8Ij5s673a FTVSjzTxiDkb1oaIF1D6gzWq+jOpRP2FLzZz5PvAY3gv2dqJSwETysTYeUL9omsgGPXJIPCZGqV5l ZE0tzq4bGlECcKw8+6QG7Wx8nc1R1nr8mcVJr4aPm23hqf8OeW/0aPD9q5xGr5MtlZ0Tfy4DL7QyJ OGCMICImmMZKlG5LBf3SMRV6JRRH2ipZSMQz6zoZwEPytCzcExbUFhvxZGzozy1hA4R8tR6/2dyQf fT6yGZ87fAjnxYortN8Wsw==; Original-Received: from [87.69.77.57] (port=4593 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nWfpx-0001im-Lf; Tue, 22 Mar 2022 10:50:29 -0400 In-Reply-To: <20220322141815.2iq7jec2d5lvfox3@Ergus> (message from Ergus on Tue, 22 Mar 2022 15:18:15 +0100) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:287356 Archived-At: > Date: Tue, 22 Mar 2022 15:18:15 +0100 > From: Ergus > Cc: Juri Linkov , larsi@gnus.org, emacs-devel@gnu.org > > > +@code{t} the completions are hidden when some unique completion is > > +executed. > > > >What do you mean by "unique completion is executed"? Both the > >"unique" and the "executed" parts need clarification. > > > unique means that, there is a single candidate o prefix so the > "added" some letter. example: compi -> compil > > The first tab shows completions but the second hides it... it is a bit > confusing compared to any other completion engine (bash, zsh, > fish)... that's why I started this changes... So we could simply say when Emacs is able to complete some characters is that right? > > If @code{completion-auto-help} is set to @code{always}, the > > +completion commands are always shown after a completion attempt, or > > > >"Commands"? didn't you mean "candidates" or "alternatives"? (The same > >problem exists in the doc string of this variable, btw.) > > > Maybe candidates is better, If it's just "better", then please explain what you mean by "commands". The text I quoted above says "the completion commands are always shown". What are those "commands" that are shown after a completion attempt? > > If the value is @code{visible}, Emacs displays completion the > > completion alternatives when it is unable to complete for the first > > time; thereafter the completion list buffer remains visible and is > > updated as you type. > > > >Is this accurate and correct? > > > "and is updated as you type." > > I am not sure that last part is accurate. updates need to update > in all cases. "as you type" suggests more an icomplete-like behavior I > thinks. Ok, so "the completion list buffer remains visible for all the subsequent completion attempts". Better? > > +current completion candidate will be highlighted with that face. The > > +default value is @code{completions-highlight}. When the value is > > +@code{nil}, no highlighting is performed. This feature sets the text > > +property @code{cursor-face}. > > > >This should explain what is "the current completion candidate". It > >isn't trivial: trying the current defaults with completion commands, I > >sometimes see a candidate highlighted, and sometimes don't. I > >couldn't figure out why. > > > > when it is not highlighting? So far the only way to not have a candidate > highlighted is when there is not candidate effectively selected (like > when completions are just updated (with no completion-auto-select) and > the cursor is before the help line; I that case there is not "current > candidate"); a return in that moment won't execute anything because > there is nothing to select, so "current completion candidate" means > that... Maybe you have a better way to explain it? Wouldn't it make sense to move point to the first candidate, so that some candidate is always highlighted? Btw, when a candidate is highlighted, it is always the first one in the list, which kinda makes me wonder why this highlighting is useful, if it always shows the candidate in a fixed location on display? > Please if you have the time change it... Otherwise I will do in some > days. Will do.