From: Dmitry Gutov <dgutov@yandex.ru>
To: Lars Ingebrigtsen <larsi@gnus.org>, Doug Davis <ddavis@ddavis.io>
Cc: 46610@debbugs.gnu.org
Subject: bug#46610: Interactive mode tagging for python.el navigation functions
Date: Thu, 18 Feb 2021 13:49:10 +0200 [thread overview]
Message-ID: <e89c0908-a587-5bca-f837-d195783912f0@yandex.ru> (raw)
In-Reply-To: <878s7ly57x.fsf@gnus.org>
On 18.02.2021 13:40, Lars Ingebrigtsen wrote:
>> This is my first stab at adding some interactive mode tagging for
>> python.el. I think that the navigation functions are the best place to
>> start; they have no use except on buffers where Python code exists and
>> it's expected that python-mode is enabled. (sent in my copyright
>> assignment paperwork today)
> Thanks; looks good. I've applied your patch to Emacs 28, as it seems
> small enough for that, but any further patches will probably have to
> wait until the assignment process has finished.
Hi Doug, Lars,
python.el is distributed as "core" package through GNU ELPA and declared
compatibility up to Emacs 24.1.
So I don't think you can use the new 'interactive' syntax there.
next prev parent reply other threads:[~2021-02-18 11:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 4:46 bug#46610: Interactive mode tagging for python.el navigation functions Doug Davis
2021-02-18 11:40 ` Lars Ingebrigtsen
2021-02-18 11:49 ` Dmitry Gutov [this message]
2021-02-18 11:52 ` Lars Ingebrigtsen
2021-02-18 14:41 ` Eli Zaretskii
2021-02-18 14:54 ` Dmitry Gutov
2021-02-18 15:07 ` Eli Zaretskii
2021-02-18 15:37 ` Dmitry Gutov
2021-02-18 17:25 ` Eli Zaretskii
2021-02-18 17:54 ` Dmitry Gutov
2021-02-18 19:47 ` Eli Zaretskii
2021-02-18 19:57 ` Dmitry Gutov
2021-02-18 20:00 ` Eli Zaretskii
2021-02-18 20:05 ` Dmitry Gutov
2021-02-18 15:50 ` Doug Davis
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=e89c0908-a587-5bca-f837-d195783912f0@yandex.ru \
--to=dgutov@yandex.ru \
--cc=46610@debbugs.gnu.org \
--cc=ddavis@ddavis.io \
--cc=larsi@gnus.org \
/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).