From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.bugs Subject: bug#50459: 28.0.50; Python shell completion is incompatible with flex, orderless, etc. Date: Thu, 09 Sep 2021 07:49:19 +0000 Message-ID: References: <87wnnsl1d1.fsf@gmail.com> <87czpijixk.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23486"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 50459@debbugs.gnu.org To: Augusto Stoffel Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Sep 09 09:50:27 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1mOEpH-0005uY-EV for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 09 Sep 2021 09:50:27 +0200 Original-Received: from localhost ([::1]:53382 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mOEpF-0003FX-QC for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 09 Sep 2021 03:50:25 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54514) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mOEou-0003FO-2C for bug-gnu-emacs@gnu.org; Thu, 09 Sep 2021 03:50:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:50750) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mOEos-0005r8-Ny for bug-gnu-emacs@gnu.org; Thu, 09 Sep 2021 03:50:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mOEos-00039J-Li for bug-gnu-emacs@gnu.org; Thu, 09 Sep 2021 03:50:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 09 Sep 2021 07:50:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 50459 X-GNU-PR-Package: emacs Original-Received: via spool by 50459-submit@debbugs.gnu.org id=B50459.163117376412047 (code B ref 50459); Thu, 09 Sep 2021 07:50:02 +0000 Original-Received: (at 50459) by debbugs.gnu.org; 9 Sep 2021 07:49:24 +0000 Original-Received: from localhost ([127.0.0.1]:34063 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mOEoG-00038E-6Z for submit@debbugs.gnu.org; Thu, 09 Sep 2021 03:49:24 -0400 Original-Received: from heytings.org ([95.142.160.155]:53298) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mOEoC-000385-Lx for 50459@debbugs.gnu.org; Thu, 09 Sep 2021 03:49:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20210101; t=1631173760; bh=PgcBu92J+TzgN7PRDfy3E3rEvn4xv0PtsYaKZJLY7II=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=IZ6/LlcIkM4NTVeNsqjdmnopHMM5E4tafNLGb5Zi04fxl1xQNiBfIHH6iY0VR0xUZ U9oLsfsaLhoDnXAP8EoVipbWnzSeHMs/bROVnjakHxMCcZh0LzBd6hbg1rdG1ijEZW kegn42m5RSi7I0sAg+JvF5RPLouLkbaka5RA4esN+ZRpGplSWhhTgtPUr920gmfQMu UjwvTgjgIJtjhGVQcxCZiMO1epdY/YZjQZB9Rat1968aaFQe4v1fbqwHGCKGaAj3/W 42lwBx+gTrzxa40ueM9HNdzMqslHd4doGjyAxF9dn5Ryx/QeMIOUJSBAZHTqJ3OUIm 5ZxzUvw6Au7pw== In-Reply-To: <87czpijixk.fsf@gmail.com> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:213884 Archived-At: >> 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".