From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.help Subject: Re: python mode bugs Date: Thu, 05 Apr 2018 17:02:23 -0400 Message-ID: References: <20180405155015.6d92e8a38c4d14ae58ecc67d@speakeasy.net> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1522962069 5193 195.159.176.226 (5 Apr 2018 21:01:09 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 5 Apr 2018 21:01:09 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Apr 05 23:01:05 2018 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1f4C0F-0001D2-W5 for geh-help-gnu-emacs@m.gmane.org; Thu, 05 Apr 2018 23:01:04 +0200 Original-Received: from localhost ([::1]:54278 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f4C2L-0002qA-F9 for geh-help-gnu-emacs@m.gmane.org; Thu, 05 Apr 2018 17:03:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53364) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f4C1m-0002pV-RP for help-gnu-emacs@gnu.org; Thu, 05 Apr 2018 17:02:39 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f4C1h-0004Cl-Vk for help-gnu-emacs@gnu.org; Thu, 05 Apr 2018 17:02:38 -0400 Original-Received: from [195.159.176.226] (port=34804 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1f4C1h-0004Cf-PT for help-gnu-emacs@gnu.org; Thu, 05 Apr 2018 17:02:33 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1f4BzY-0000PS-SP for help-gnu-emacs@gnu.org; Thu, 05 Apr 2018 23:00:20 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 35 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:5CIxECoTLWMGRvPgxbTHJx8L+yw= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:116359 Archived-At: > 3. At 111 days old, it doesn't seem like the known bug is getting any > attention. What is the polite way to indicate it matters? You can send a new message to that bug-report with a shirt content like "ping?" or "Is anybody here? it's been 111 days and I still haven't heard anything". Even better, you can add info such as the one you provide below: > In case you *really* want to help, the offending function appears to be > > python-imenu--build-tree > > and the regex > > python-nav-beginning-of-defun-regexp > > The difference in the pattern to be matched is: > > def f(a, b): #works > vs > def f(a: int, b: str) -> bool: # fails > > FWIW, I don't think the regex need include anything after the leading > parenthesis. The following awk script is too simple because it doesn't > recognize nested functions and class methods, but otherwise does the > trick: > > awk -F'[\t ()]' '/^def +/ {print $2}' which might allow even Emacs contributors not familiar with Python to come up with a fix. Stefan