From: "João Távora" <joaotavora@gmail.com>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: Daniel Mendler <mail@daniel-mendler.de>,
Gregory Heytings <gregory@heytings.org>,
48545@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#48545: 28.0.50; `icomplete-vertical-mode` does not support the `group-function`
Date: Thu, 19 Aug 2021 14:29:17 +0100 [thread overview]
Message-ID: <CALDnm50zipcHuvNWkaFTC5ZiERoyH=JC=pFDHywVkcfs76t+kA@mail.gmail.com> (raw)
In-Reply-To: <87zgtdd2yi.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
On Thu, Aug 19, 2021, 13:38 Kévin Le Gouguec <kevin.legouguec@gmail.com>
wrote:
> João Távora <joaotavora@gmail.com> writes:
>
> FWIW (I didn't take the time to understand the ins and outs of the
> completion system nor the changes that are being made; sorry about
> that),
Don't beat yourself over it, it's not an easy or pleasent thing to
understand.
with this tentative patch, Icomplete seems to honour
> read-char-by-name-sort. With icomplete enabled and
> read-char-by-name-sort set to 'code, try
>
> C-x 8 RET CLOCK FACE
>
> - with the current master branch, the completions are sorted
> alphabetically,
> - with the tentative patch applied, the completions are sorted by code
> point.
>
Yes I think that's the idea. But do you think that's good or bad?
This seems to compose well with completions-group AFAICT (see e.g. C-x 8
> RET ROMAN).
>
This is good, right?
João
>
[-- Attachment #2: Type: text/html, Size: 2492 bytes --]
next prev parent reply other threads:[~2021-08-19 13:29 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 [this message]
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
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='CALDnm50zipcHuvNWkaFTC5ZiERoyH=JC=pFDHywVkcfs76t+kA@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=48545@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=gregory@heytings.org \
--cc=kevin.legouguec@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.