From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Tassilo Horn Newsgroups: gmane.emacs.devel Subject: Re: [GNU ELPA] New package proposal: aggressive-completion.El Date: Sat, 03 Apr 2021 20:03:48 +0200 Message-ID: <87wntjw7ai.fsf@gnu.org> References: <87o8evok58.fsf@gnu.org> <87y2dza8g5.fsf@posteo.net> <87tuonwk8b.fsf@gnu.org> <87pmzb9tc2.fsf_-_@posteo.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="37725"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.5.11; emacs 28.0.50 Cc: emacs-devel@gnu.org To: Philip Kaludercic Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Apr 03 20:32:08 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 1lSl42-0009gI-Rm for ged-emacs-devel@m.gmane-mx.org; Sat, 03 Apr 2021 20:32:06 +0200 Original-Received: from localhost ([::1]:48986 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lSl41-0006uu-TR for ged-emacs-devel@m.gmane-mx.org; Sat, 03 Apr 2021 14:32:05 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58690) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lSl1n-0006FA-W5 for emacs-devel@gnu.org; Sat, 03 Apr 2021 14:29:48 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:57371) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lSl1n-0001sV-4R; Sat, 03 Apr 2021 14:29:47 -0400 Original-Received: from auth2-smtp.messagingengine.com ([66.111.4.228]:36983) by fencepost.gnu.org with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.82) (envelope-from ) id 1lSl1m-0003g2-Q7; Sat, 03 Apr 2021 14:29:46 -0400 Original-Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailauth.nyi.internal (Postfix) with ESMTP id 3C93827C0054; Sat, 3 Apr 2021 14:29:46 -0400 (EDT) Original-Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sat, 03 Apr 2021 14:29:46 -0400 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudeikedgudefudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpehffgfhvffuffgjkfggtgesthdtredttdertdenucfhrhhomhepvfgrshhs ihhlohcujfhorhhnuceothhsughhsehgnhhurdhorhhgqeenucggtffrrghtthgvrhhnpe evveeikeetkeeviefgfeffiedvteeguddvffeuueduveegtddthedvhfeuveffhfenucfk phepkeejrdduieefrdefuddrudehgeenucevlhhushhtvghrufhiiigvpedtnecurfgrrh grmhepmhgrihhlfhhrohhmpehthhhorhhnodhmvghsmhhtphgruhhthhhpvghrshhonhgr lhhithihqdekieejfeekjeekgedqieefhedvleekqdhtshguhheppehgnhhurdhorhhgse hfrghsthhmrghilhdrfhhm X-ME-Proxy: Original-Received: from thinkpad-t440p (p57a31f9a.dip0.t-ipconnect.de [87.163.31.154]) by mail.messagingengine.com (Postfix) with ESMTPA id 58599240066; Sat, 3 Apr 2021 14:29:45 -0400 (EDT) In-reply-to: <87pmzb9tc2.fsf_-_@posteo.net> 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:267358 Archived-At: Philip Kaludercic writes: >>> 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. What do you mean it affects only the first letter? I mean, obviously that's where it is slowest because the number of completions is the largest you can get for that letter, no? > 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. Yes, because aggressive-completion (completion or completion help) kick in after `aggressive-completion-delay' seconds. The default value is 0.3. You might want to try a smaller delay for added snappiness but I guess that will become inconvenient in other case, e.g., when you mistype. >>> 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. Yes, hopefully, that's intended. >> 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. Well, aggressive-completion is pretty much such a bird with spiral spring legs hacking its beak onto your TAB key every 0.3 seconds after you've edited your input. ;-) > 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. I can understand that desire but I'm not sure if aggressive-completion.el is the right place for such a feature. IMHO, the standard *Completions* buffer window's size should be customizable directly in emacs if at all... Oh, well, does `temp-buffer-resize-mode' with its limits `temp-buffer-max-height' and `temp-buffer-max-width' already do what you want? Bye, Tassilo