From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#51010: 29.0.50; python completion breaks upon non-trivial rl config Date: Wed, 20 Oct 2021 14:53:38 +0300 Message-ID: <83lf2nc3p9.fsf@gnu.org> References: <88E85B14-518F-4F18-B2F0-96BA2FDA981C@gmail.com> <878rz1xfn4.fsf@gmail.com> <83zgrckqj3.fsf@gnu.org> <83h7dikce4.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32794"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 51010@debbugs.gnu.org To: Carlos Pita Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Oct 20 13:54: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 1mdAAt-0008JG-7J for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 20 Oct 2021 13:54:27 +0200 Original-Received: from localhost ([::1]:35128 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mdAAr-0001Dt-8I for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 20 Oct 2021 07:54:25 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38976) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mdAAV-0001DX-2b for bug-gnu-emacs@gnu.org; Wed, 20 Oct 2021 07:54:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:41350) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mdAAU-0000Oy-0G for bug-gnu-emacs@gnu.org; Wed, 20 Oct 2021 07:54:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mdAAT-0006ke-Vh for bug-gnu-emacs@gnu.org; Wed, 20 Oct 2021 07:54:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 20 Oct 2021 11:54:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 51010 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 51010-submit@debbugs.gnu.org id=B51010.163473081825903 (code B ref 51010); Wed, 20 Oct 2021 11:54:01 +0000 Original-Received: (at 51010) by debbugs.gnu.org; 20 Oct 2021 11:53:38 +0000 Original-Received: from localhost ([127.0.0.1]:52896 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mdAA1-0006ja-5D for submit@debbugs.gnu.org; Wed, 20 Oct 2021 07:53:38 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:37028) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mdA9z-0006jM-Gz for 51010@debbugs.gnu.org; Wed, 20 Oct 2021 07:53:31 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:35118) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mdA9u-0008JA-7Y; Wed, 20 Oct 2021 07:53:26 -0400 Original-Received: from [87.69.77.57] (port=4284 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mdA9t-00011N-R3; Wed, 20 Oct 2021 07:53:26 -0400 In-Reply-To: (message from Carlos Pita on Tue, 19 Oct 2021 20:20:08 -0300) 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:217655 Archived-At: > From: Carlos Pita > Date: Tue, 19 Oct 2021 20:20:08 -0300 > Cc: 51010@debbugs.gnu.org > > If a message to the bug tracker contains a patch, please > include the string "[PATCH]" in the subject of the message in order to > let the bug tracker tag the bug properly. > > (I was under the impression that the patch tag was the official way of > doing it.) > > Now, supposing that the patch is an addendum to an ongoing thread, > wouldn't that "[PATCH]" marker mess with the organization of your > emails? Yes, depending on the MUA. Although it's not a catastrophe. So please use that only when the reason for bug report is to suggest a patch.