From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Nitish <nitishch@protonmail.com>, 30822@debbugs.gnu.org
Subject: bug#30822: 25.3; python-shell-send-defun sends only one line
Date: Wed, 11 Apr 2018 19:29:20 +0200 [thread overview]
Message-ID: <97f165a5-92eb-58cb-2a61-b4d62daeeec9@easy-emacs.de> (raw)
In-Reply-To: <CAM-tV-8S-PhaDLE2GVHchXa677xnnJgNuUcjjH9snfV+7R4GRw@mail.gmail.com>
On 11.04.2018 16:57, Noam Postavsky wrote:
> On 11 April 2018 at 10:49, Andreas Röhler <andreas.roehler@easy-emacs.de> wrote:
>> On 09.04.2018 13:56, Noam Postavsky wrote:
>>>
>>> Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
>>>
>>>> Please consider re-opening.
>>>> Isn't this a bug of python-nav-beginning-of-defun and the fix
>>>> belonging there?
>>>
>>> I don't see why. If you have a bug to report against
>>> python-nav-beginning-of-defun please just say what you mean.
>>
>> Well, if a function is decorated, shouldn't a command reaching the start of
>> def now reach the start of decorator?
>
> Changing python-nav-beginning-of-defun to behave that way sounds
> reasonable, but it should be pursued in a separate (wishlist) bug, not
> this one.
>
Or fixing the bug here at the right place solves two at once?
next prev parent reply other threads:[~2018-04-11 17:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 20:05 bug#30822: 25.3; python-shell-send-defun sends only one line David Liu
2018-03-14 20:37 ` David Liu
2018-03-15 0:22 ` Noam Postavsky
2018-04-06 3:22 ` Nitish
2018-04-07 2:26 ` Noam Postavsky
2018-04-07 2:45 ` Nitish
2018-04-07 3:01 ` Noam Postavsky
2018-04-07 3:37 ` Nitish
2018-04-08 16:07 ` Noam Postavsky
2018-04-08 16:21 ` Nitish
2018-04-08 16:44 ` Noam Postavsky
2018-04-09 6:12 ` Andreas Röhler
2018-04-09 11:56 ` Noam Postavsky
2018-04-11 14:49 ` Andreas Röhler
2018-04-11 14:57 ` Noam Postavsky
2018-04-11 17:29 ` Andreas Röhler [this message]
2018-04-11 17:33 ` Noam Postavsky
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=97f165a5-92eb-58cb-2a61-b4d62daeeec9@easy-emacs.de \
--to=andreas.roehler@easy-emacs.de \
--cc=30822@debbugs.gnu.org \
--cc=nitishch@protonmail.com \
--cc=npostavs@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 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.