From: Tassilo Horn <tsdh@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: [GNU ELPA] New package proposal: aggressive-completion.El
Date: Sat, 03 Apr 2021 20:03:48 +0200 [thread overview]
Message-ID: <87wntjw7ai.fsf@gnu.org> (raw)
In-Reply-To: <87pmzb9tc2.fsf_-_@posteo.net>
Philip Kaludercic <philipk@posteo.net> 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
next prev parent reply other threads:[~2021-04-03 18:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 7:53 [GNU ELPA] New package proposal: aggressive-completion.el Tassilo Horn
2021-04-03 8:37 ` Tassilo Horn
2021-04-03 9:11 ` Manuel Uberti
2021-04-03 9:42 ` Tassilo Horn
2021-04-03 10:14 ` Jean Louis
2021-04-03 11:17 ` Jean Louis
2021-04-03 10:07 ` Jean Louis
2021-04-03 9:36 ` Jean Louis
2021-04-03 10:03 ` Tassilo Horn
2021-04-03 10:19 ` Jean Louis
2021-04-03 10:24 ` Tassilo Horn
2021-04-04 13:53 ` Basil L. Contovounesios
2021-04-04 19:05 ` Tassilo Horn
2021-04-04 20:12 ` T.V Raman
2021-04-05 7:01 ` Tassilo Horn
2021-04-05 14:21 ` T.V Raman
2021-04-04 20:26 ` Stefan Monnier
2021-04-05 7:17 ` Tassilo Horn
2021-04-03 9:49 ` Jean Louis
2021-04-03 10:05 ` Tassilo Horn
2021-04-03 11:53 ` Philip Kaludercic
2021-04-03 11:55 ` Philip Kaludercic
2021-04-03 13:43 ` Tassilo Horn
2021-04-03 17:22 ` [GNU ELPA] New package proposal: aggressive-completion.El Philip Kaludercic
2021-04-03 18:03 ` Tassilo Horn [this message]
2021-04-03 14:04 ` [GNU ELPA] New package proposal: aggressive-completion.el Stefan Monnier
2021-04-03 18:29 ` Tassilo Horn
2021-04-03 19:30 ` Tassilo Horn
2021-04-03 21:01 ` Stefan Monnier
2021-04-03 20:02 ` Gabriel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wntjw7ai.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).