all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: 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 12:40:02 +0100	[thread overview]
Message-ID: <878s7ly57x.fsf@gnus.org> (raw)
In-Reply-To: <m2pn0y9e53.fsf@ddavis.io> (Doug Davis's message of "Wed, 17 Feb 2021 23:46:32 -0500")

Doug Davis <ddavis@ddavis.io> writes:

> 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.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-02-18 11:40 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 [this message]
2021-02-18 11:49   ` Dmitry Gutov
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878s7ly57x.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=46610@debbugs.gnu.org \
    --cc=ddavis@ddavis.io \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.