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: Updating *Completions* as you type Date: Fri, 13 Oct 2023 09:31:05 +0300 Message-ID: <83fs2ft4nq.fsf@gnu.org> References: <87bkd3z9bi.fsf@catern.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14881"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: sbaugh@catern.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Oct 13 08:32:35 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 1qrBis-0003gB-Va for ged-emacs-devel@m.gmane-mx.org; Fri, 13 Oct 2023 08:32:35 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qrBhZ-0001cm-48; Fri, 13 Oct 2023 02:31:13 -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 1qrBhV-0001cV-Pj for emacs-devel@gnu.org; Fri, 13 Oct 2023 02:31:10 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qrBhV-0006cO-CI; Fri, 13 Oct 2023 02:31:09 -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=7xwpOY8+vJrexNYB6ScomwB1YqFea6SskxS25AtUUeo=; b=Rr4uUQna11VJ sfV+KtZ+PzeNqJ+Gd9HBUSYPASVAIfvdvA0CW/TQp09fYXKNvo6z/+bwJhjfZEEbnp57RWPM66ktL AXqThYUrImEdUu6ZnYNpkxPbIK1E6colHeur6xt4CuamexFiU0GzeAFIvQ4BHRa654IHXp+MwaLbq zoYKTuBYuHpxR2UKQz3Ae4k+Kt88PLtihN7bQF3kQ/1rfjWrrIO7AsGDOqtAvPDonW0ntSz4WfK99 +Sbh8bQ7pNb/LHgb6MOA/RSGsMxEqDcwbry0vVYupFJ70DCIA4LdjEFqrcmKs1IwK+WnP61bmMm6g 8IPApFvdyw2doD9fj+nFww==; In-Reply-To: <87bkd3z9bi.fsf@catern.com> (sbaugh@catern.com) 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:311428 Archived-At: > 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? > (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.