From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Philip Kaludercic Newsgroups: gmane.emacs.devel Subject: Re: [GNU ELPA] New package proposal: aggressive-completion.El Date: Sat, 03 Apr 2021 19:22:05 +0200 Message-ID: <87pmzb9tc2.fsf_-_@posteo.net> References: <87o8evok58.fsf@gnu.org> <87y2dza8g5.fsf@posteo.net> <87tuonwk8b.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="27396"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) Cc: emacs-devel@gnu.org To: Tassilo Horn Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Apr 03 19:22:48 2021 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 1lSjyx-000718-AV for ged-emacs-devel@m.gmane-mx.org; Sat, 03 Apr 2021 19:22:47 +0200 Original-Received: from localhost ([::1]:59204 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lSjyw-0003WV-Cm for ged-emacs-devel@m.gmane-mx.org; Sat, 03 Apr 2021 13:22:46 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49440) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lSjyP-00034i-Rx for emacs-devel@gnu.org; Sat, 03 Apr 2021 13:22:13 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]:59031) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lSjyN-0004wG-Jx for emacs-devel@gnu.org; Sat, 03 Apr 2021 13:22:13 -0400 Original-Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id E40F12400FB for ; Sat, 3 Apr 2021 19:22:06 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1617470526; bh=YcC7WIfcWBK2v+Gq+ZEy5pnaVv9spZGZGv2y6/2zqr4=; h=From:To:Cc:Subject:Date:From; b=DAyr8vQmWlvM2pADiEYAYtYBwXBXVq/SMB5f8E0sFi1KKXcUcr9HyMlnms/hmJSlf 9KRsanpG19x0GqeNhzy16E3kg8u7tVzgta6jTc51tj86Ni4vP9E38383Ob630PDOR2 GWJ6cAsqsy1t0nSLaiYzNqKfVrgn/xuPd4yPXP/njuA9sSw9GkMNJZRGUI/BMlHN1B +lsuWncTxzjdTMDbXOuQZXicQmFV8Y54F0jiBUY3lHPRT+Zr8ZIWKwlvyVo4A7p0Ma kJucL0UnmOkZH1aMZcG6UJyle6YE43NYHJdoZ1aKBFKvc+H+zAf+ZFbMk4fdbNTg9d tpC0PVG9rJh7A== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4FCNyQ2WzSz9rxG; Sat, 3 Apr 2021 19:22:06 +0200 (CEST) In-Reply-To: <87tuonwk8b.fsf@gnu.org> (Tassilo Horn's message of "Sat, 03 Apr 2021 15:43:23 +0200") Received-SPF: pass client-ip=185.67.36.66; envelope-from=philipk@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:267353 Archived-At: Tassilo Horn writes: > Philip Kaludercic writes: > > Hi Philip, > >> Just tried out the package, and it seems to work very well! I just >> have two annoyances: >> >> 1. Where there are too many options, lag is noticeable (eg. with C-h o). > > There's a knob for that: `aggressive-completion-max-shown-completions'. Sadly it still persists. All in all it is barley noticeable, and it only affects the first letter in my case. Maybe you can replicate it: C-h o a [wait] on my system there is about half a second of lag between typing a and a appearing on the screen. If I typo more letter, they are all delayed by half a second. >> 2. The completion buffer keeps appearing and disappearing, shrinking >> and growing. > > The *Completions* buffer should appear as soon as there is at least one > and at most `aggressive-completion-max-shown-completions' completions, > and it'll disappear when completion selected a unique match. Do you see > something different? No, but if I remove a word and the completion is not unique any more, the buffer re-appears. > Wrt. the resizing: that's the standard completion help behavior you'd > also see when double-TAB-ing during completion. Not sure if there's a > way to restrict that window's height. Yes, but my point was that the change in window height is in response to a manual completion request. This might just be me, but I try to avoid "undeterministic" behaviour, or at least effects that I cannot infer from my actions. I cannot say for sure, but I think that if you could force the completion buffer to stay at one place during the entire completion, this would be preferable. > Bye, > Tassilo > > -- Philip K.