unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Yilin Wei <yilin.wei10@gmail.com>, 36700@debbugs.gnu.org
Subject: bug#36700: 27.0.50; python-mode beginning-of-defun broken
Date: Tue, 25 Aug 2020 17:26:00 -0700	[thread overview]
Message-ID: <CADwFkmnJWeQ5ATjD+sefb7fLfTNWZv5amyy977W_hZ386BBgfg@mail.gmail.com> (raw)
In-Reply-To: <87ef2pzdr2.fsf@gmail.com> (Noam Postavsky's message of "Tue, 16 Jul 2019 20:49:37 -0400")

tags 36700 + notabug
close 36700
thanks

Noam Postavsky <npostavs@gmail.com> writes:

> Yilin Wei <yilin.wei10@gmail.com> writes:
>
>> def moo():
>>     class Test:
>>       pass
>>     <-
>>
>> When the cursor is at the location marked, running (beginning-of-defun)
>> makes the cursor go to the wrong location, shown below, instead of to
>> the beginning of the def.
>>
>> def moo():
>> <-   class Test:
>>        pass
>
> I don't think this is a bug, python.el just takes a more liberal
> interpretation of "defun" that includes class definitions.  See for
> example, python-nav-beginning-of-defun-regexp:
>
>     (defvar python-nav-beginning-of-defun-regexp
>                                     ^^^^^^^^^^^^
>       (python-rx line-start (* space) defun (+ space) (group symbol-name))
>       "Regexp matching class or function definition.
>                        ^^^^^^^^^^^^^^^^^

I agree with Noam here, and seeing as there has been no further replies
within 1 year, I'm therefore closing this bug report.





      reply	other threads:[~2020-08-26  0:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-16 23:59 bug#36700: 27.0.50; python-mode beginning-of-defun broken Yilin Wei
2019-07-17  0:49 ` Noam Postavsky
2020-08-26  0:26   ` Stefan Kangas [this message]

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=CADwFkmnJWeQ5ATjD+sefb7fLfTNWZv5amyy977W_hZ386BBgfg@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=36700@debbugs.gnu.org \
    --cc=npostavs@gmail.com \
    --cc=yilin.wei10@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).