From: Gregory Heytings <gregory@heytings.org>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: 50459@debbugs.gnu.org
Subject: bug#50459: 28.0.50; Python shell completion is incompatible with flex, orderless, etc.
Date: Thu, 09 Sep 2021 07:49:19 +0000 [thread overview]
Message-ID: <cd485de4cd6bd29c005f@heytings.org> (raw)
In-Reply-To: <87czpijixk.fsf@gmail.com>
>> You shouldn't use (setq completion-styles '(flex)), you should use
>> (add-to-list 'completion-styles 'flex). Otherwise the default
>> completion styles are not used anymore.
>
> This doesn't change the issue described in the subject line. I would
> still not see any flex completions if I did what you suggest.
>
Because the flex completion mechanism returns no completions, and the next
completion mechanism is called. What kind of flex completions would you
expect to see after x.t TAB in your example?
>
> Granted, completion wouldn't be totally broken. But I don't mind
> letting the brokenness manifest itself. Therefore I use (setq
> completion-styles '(orderless)).
>
It's not broken, it works as designed. Instead of asking each user of the
completion mechanism to implement a specific function for substring / flex
completion, these mechanisms tell them "please return all possible
completions, I'll do the filtering job for you".
next prev parent reply other threads:[~2021-09-09 7:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 17:52 bug#50459: 28.0.50; Python shell completion is incompatible with flex, orderless, etc Augusto Stoffel
2021-09-08 17:44 ` Augusto Stoffel
2021-09-09 7:11 ` Michael Albinus
2021-09-09 7:32 ` Gregory Heytings
2021-09-09 7:30 ` Gregory Heytings
2021-09-09 7:40 ` Augusto Stoffel
2021-09-09 7:49 ` Gregory Heytings [this message]
2021-09-09 8:45 ` Augusto Stoffel
2021-09-09 8:50 ` Gregory Heytings
2021-09-09 16:46 ` Augusto Stoffel
2021-09-10 11:37 ` Lars Ingebrigtsen
2021-09-10 11:50 ` Augusto Stoffel
2021-09-10 13:14 ` João Távora
2021-09-10 13:28 ` Dmitry Gutov
2021-09-10 14:06 ` João Távora
2021-09-10 14:22 ` Dmitry Gutov
2021-09-10 14:39 ` João Távora
2021-09-10 14:43 ` Dmitry Gutov
2021-09-10 19:27 ` Augusto Stoffel
2021-09-10 20:08 ` João Távora
2021-09-11 12:09 ` Lars Ingebrigtsen
2021-09-11 12:34 ` Augusto Stoffel
2021-09-11 12:36 ` Lars Ingebrigtsen
2021-09-10 13:32 ` Dmitry Gutov
2021-09-10 19:08 ` bug#50459: 28.0.50; [PATCH] " Augusto Stoffel
2021-09-11 12:50 ` Lars Ingebrigtsen
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=cd485de4cd6bd29c005f@heytings.org \
--to=gregory@heytings.org \
--cc=50459@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
/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).