From: Dmitry Gutov <dgutov@yandex.ru>
To: "João Távora" <joaotavora@gmail.com>
Cc: Daniel Mendler <mail@daniel-mendler.de>, 48545@debbugs.gnu.org
Subject: bug#48545: 28.0.50; `icomplete-vertical-mode` does not support the `group-function`
Date: Sun, 22 Aug 2021 16:52:02 +0300 [thread overview]
Message-ID: <09afb635-ca5d-cee5-2ea9-b119e2720cec@yandex.ru> (raw)
In-Reply-To: <874kbjq88p.fsf@gmail.com>
On 21.08.2021 15:42, João Távora wrote:
> Dmitry Gutov<dgutov@yandex.ru> writes:
>
>> On 21.08.2021 12:40, João Távora wrote:
>>> Yes, I think you see what you mean. But I also imagine it would be
>>> terrifyingly confusing for a user of a scrolling dropdown to see
>>> candidates jump back and forth into their groups as the user scrolls
>>> down to see a new candidate and hide another. If what I imagine isn't
>>> what you mean, maybe you could code something up and show what you mean.
>> I suppose yes, if you only group candidates that are visible on the
>> screen, it could lead to jumping. Good point. Then I would suggest to
>> go back to "global" grouping.
> Then do. Go back to that experiment and its drawbacks and actually
> prototype it the way you envision it. Then share results here.
I don't think I'm obligated to support every trivial suggestion with a
patch and a benchmark.
Or explain, from various POVs, why removing the sorting step "because
it's expensive" is faulty reasoning.
Or why the grouping approach in icomplete mode should match what the
default UI does and what other completion UIs (from which the grouping
feature was extracted) do as well.
Whatever, do what you like. I'm out of this thread.
next prev parent reply other threads:[~2021-08-22 13:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 18:56 bug#48545: 28.0.50; `icomplete-vertical-mode` does not support the `group-function` Daniel Mendler
2021-08-17 12:17 ` João Távora
2021-08-18 9:38 ` Kévin Le Gouguec
2021-08-18 9:55 ` João Távora
2021-08-19 11:18 ` João Távora
2021-08-19 12:38 ` Kévin Le Gouguec
2021-08-19 13:29 ` João Távora
2021-08-19 19:36 ` Kévin Le Gouguec
2021-08-19 15:02 ` Dmitry Gutov
2021-08-19 19:41 ` João Távora
2021-08-19 22:37 ` Dmitry Gutov
2021-08-19 23:39 ` João Távora
2021-08-19 23:51 ` Dmitry Gutov
2021-08-20 10:35 ` João Távora
2021-08-21 2:09 ` Dmitry Gutov
2021-08-21 9:40 ` João Távora
2021-08-21 12:01 ` Dmitry Gutov
2021-08-21 12:42 ` João Távora
2021-08-22 13:52 ` Dmitry Gutov [this message]
2021-08-22 15:44 ` João Távora
2021-08-21 0:24 ` João Távora
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=09afb635-ca5d-cee5-2ea9-b119e2720cec@yandex.ru \
--to=dgutov@yandex.ru \
--cc=48545@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=mail@daniel-mendler.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.