From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: sbaugh@catern.com Newsgroups: gmane.emacs.devel Subject: Re: Updating *Completions* as you type Date: Tue, 17 Oct 2023 11:01:01 -0400 Message-ID: <87o7gxwaxe.fsf@catern.com> References: <87bkd3z9bi.fsf@catern.com> <86cyxjyr1y.fsf@mail.linkov.net> <86r0lxm7um.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21511"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-devel@gnu.org Cancel-Lock: sha1:yeoXQuVowGOj+U8Cs661lW0Hsw0= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Oct 17 17:12:42 2023 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 1qslkQ-0005LA-4I for ged-emacs-devel@m.gmane-mx.org; Tue, 17 Oct 2023 17:12:42 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qsljV-00043I-0H; Tue, 17 Oct 2023 11:11:45 -0400 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 1qslZJ-0000fj-1c for emacs-devel@gnu.org; Tue, 17 Oct 2023 11:01:13 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qslZH-0001Ig-HY for emacs-devel@gnu.org; Tue, 17 Oct 2023 11:01:12 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1qslZF-0009uv-Jq for emacs-devel@gnu.org; Tue, 17 Oct 2023 17:01:09 +0200 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -15 X-Spam_score: -1.6 X-Spam_bar: - X-Spam_report: (-1.6 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Tue, 17 Oct 2023 11:11:41 -0400 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:311539 Archived-At: Tangentially, Juri, I have a thought about a redesign of minibuffer-next-completion and minibuffer-choose-completion. What if the concept of "current selected completion" was unified with "the default completion"? This could be a nice, general UI. Specifically, with switch-to-buffer and a default of init.el: - If init.el is present in *Completions*, start out with point on it. This would be purely a display nicety, it wouldn't actually affect anything yet. (This would be easy with my patch which I posted elsewhere in this thread to preserve the location of point in *Completions*) - If and when the user invokes minibuffer-next-completion: - The default changes to whatever the new selected completion is - The prompt text "(default init.el)" changes permanently to literally "(default selected completion)" - RET, as always, chooses the default if the minibuffer is empty; if the user has done minibuffer-next-completion, the default is the selected completion, so RET will choose that. - M-RET (minibuffer-choose-completion) is replaced with a new command which immediately chooses the default, whatever it is, ignoring the current contents of the minibuffer - C-u M-RET inserts the default in the the minibuffer, without exiting (matching the behavior of C-u minibuffer-choose-completion) I think this has some nice benefits in reducing the number of concepts people need to track. If the minibuffer is empty, they can just use minibuffer-next-completion a few times followed by RET to select a completion, no need to use M-RET. Plus, the new M-RET and C-u M-RET would be useful even to users who don't use minibuffer-next-completion. I also think this would make it less painful to set minibuffer-completion-auto-choose to nil, which matches completion-in-region better and also works much better with completions-auto-update.