From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Spencer Baugh Newsgroups: gmane.emacs.devel Subject: Re: Updating *Completions* as you type Date: Fri, 13 Oct 2023 14:01:38 -0400 Message-ID: References: <87bkd3z9bi.fsf@catern.com> <83fs2ft4nq.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9646"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-devel@gnu.org Cancel-Lock: sha1:UDlQ9Hw1nnyGWWydKyxK3BIFt00= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Oct 14 08:06:55 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 1qrXnZ-0002Fg-SG for ged-emacs-devel@m.gmane-mx.org; Sat, 14 Oct 2023 08:06:53 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qrXmk-0000hK-Ce; Sat, 14 Oct 2023 02:06:02 -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 1qrMTv-0006Hh-5E for emacs-devel@gnu.org; Fri, 13 Oct 2023 14:01:52 -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 1qrMTs-0006So-D6 for emacs-devel@gnu.org; Fri, 13 Oct 2023 14:01:50 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1qrMTp-00069y-2t for emacs-devel@gnu.org; Fri, 13 Oct 2023 20:01:45 +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: Sat, 14 Oct 2023 02:06:01 -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:311439 Archived-At: Eli Zaretskii writes: >> From: sbaugh@catern.com >> Date: Thu, 12 Oct 2023 19:53:53 -0400 >> >> >> It would be nice if there was a built-in customization which caused >> *Completions* to update as you type, as long as that buffer is visible. >> I imagine such a request has been made before, so what is the obstacle >> to adding it? > > I think we have alternative completion schemes, like ido.el and > others, which update the list of the completion candidates as you > type, albeit not in the *Completions* buffer. Why would we need yet > another knob in the default completion scheme? ido-mode only works for files and buffers, not all minibuffer completion, and is also unmaintained and sometimes buggy besides that. icomplete-mode (and its derivatives) doesn't work for in-buffer completion. Also, it is buggier than the default completion scheme. >> (Btw, if we had this behavior, it also seems like it would help with >> another long-time request: asynchronous completion support. A >> programmed completion table could internally do something asynchronous >> and stateful, and accumulate results over time, and return more and more >> results each time Emacs calls all-completions/try-completion. If Emacs >> automatically called all-completions with such a programmed completion >> table, the resulting behavior would be an acceptable approximation of >> asynchronous completion, without having to complicate the programmed >> completion API.) > > IIUC what you mean by "asynchronous completion", it is a terrible > idea. How can anyone type text without getting immediate feedback for > what he/she typed? When I sometimes see this (due to network delays > or system load or whatever), it is a terrible UX. By asynchronous completion, I just mean being able to type, and trigger completion, and have completions appear incrementally as they are computed, without interfering with you continuing to type. I don't think that stops immediate feedback for typing.