From: npostavs@users.sourceforge.net
To: Dmitry Lazurkin <dilaz03@gmail.com>
Cc: 24820@debbugs.gnu.org
Subject: bug#24820: Imenu in `python-mode' does not display function name for async def
Date: Thu, 12 Jan 2017 20:49:07 -0500 [thread overview]
Message-ID: <87pojrzq3w.fsf@users.sourceforge.net> (raw)
In-Reply-To: <e7946128-5170-88cd-8ea0-9890705ab61f@gmail.com> (Dmitry Lazurkin's message of "Fri, 6 Jan 2017 22:41:21 +0300")
tags 24820 fixed
close 24820 26.1
quit
Dmitry Lazurkin <dilaz03@gmail.com> writes:
> On 01/06/2017 05:00 PM, npostavs@users.sourceforge.net wrote:
>> So, why is that a problem?
>
> This is not problem for me.
Okay, then I'm not quite sure what we were talking about. Anyway, like
I said before, your patch looks fine so I've pushed it to master [1:
d4a9708]. I added "(Bug#24820)" to the commit, but I didn't change the
code.
1: 2017-01-12 20:40:19 -0500 d4a97088f69eb5729261ee4581cfb7d60c673ebd
Fix extracting async def type and name in python mode imenu
next prev parent reply other threads:[~2017-01-13 1:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 14:34 bug#24820: Imenu in `python-mode' does not display function name for async def Dmitry Lazurkin
2016-12-23 17:32 ` bug#24820: Any suggestions about patch? Dmitry Lazurkin
2016-12-26 22:26 ` npostavs
2017-01-04 16:48 ` bug#24820: I think copyright is assigned Dmitry Lazurkin
2017-01-04 16:55 ` Eli Zaretskii
2017-01-04 20:24 ` bug#24820: Rebase against master Dmitry Lazurkin
2017-01-04 20:27 ` Dmitry Lazurkin
2017-01-05 4:07 ` bug#24820: Imenu in `python-mode' does not display function name for async def npostavs
2017-01-05 10:14 ` Dmitry Lazurkin
2017-01-06 1:19 ` npostavs
2017-01-06 12:07 ` Dmitry Lazurkin
2017-01-06 14:00 ` npostavs
2017-01-06 19:41 ` Dmitry Lazurkin
2017-01-13 1:49 ` npostavs [this message]
2017-01-13 9:34 ` dilaz03 .
2017-01-05 20:20 ` Dmitry Lazurkin
2017-01-05 21:03 ` Dmitry Lazurkin
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=87pojrzq3w.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=24820@debbugs.gnu.org \
--cc=dilaz03@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).