From: JD Smith <jdtsmith@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 47657@debbugs.gnu.org
Subject: bug#47657: python-shell font-lock with multi-line input: runaway fontification buffer length
Date: Tue, 13 Apr 2021 09:14:20 -0400 [thread overview]
Message-ID: <1971BD45-05FC-4124-8A3C-7EBC968D55D5@gmail.com> (raw)
In-Reply-To: <87fszusj6z.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 1323 bytes --]
> On Apr 13, 2021, at 4:05 AM, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> JD Smith <jdtsmith@gmail.com> writes:
>
>> Do you have a step-by-step recipe, starting from "emacs -Q", to
>> reproduce this problem?
>>
>> 1 emacs -Q
>> 2 M-x run-python
>> 3 C-x 5 b “ *Python-font-lock*”
>> 4 In inferior python shell: type any line.
>> 5 C-c SPC (`comint-accumulate’) to continue.
>> 6 Type another line. Notice the first line is repeated.
>> 7 Repeat steps 5 & 6 several times.
>
> You didn't say what Emacs version you're using -- I tested this in Emacs
> 28, and was unable to reproduce this. The " *Python-font-lock*" buffer
> never contains more than a single non-blank line using this recipe.
> (The "any line" I used to test was "5”.)
Mac port, v27.2, python-mode v0.26.1. I have a hard time understanding how this would not reproduce, as (buffer-substring-no-properties prompt-end (point-max)) clearly takes all of the text (multi-lines included) from the prompt onward. I took a look here <https://github.com/emacs-mirror/emacs/blob/b064ddd3f600ed28e62b09d556ecced5f80d9883/lisp/progmodes/python.el#L2710> (python-mode v0.27.1) and the input is gathered in the same manner in the post-command-hook. The “repeated” lines in #6 are in the *Python-font-lock* buffer, btw.
[-- Attachment #2: Type: text/html, Size: 2341 bytes --]
next prev parent reply other threads:[~2021-04-13 13:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 15:48 bug#47657: python-shell font-lock with multi-line input: runaway fontification buffer length JD Smith
2021-04-12 9:32 ` Lars Ingebrigtsen
2021-04-12 13:18 ` JD Smith
2021-04-13 8:05 ` Lars Ingebrigtsen
2021-04-13 13:14 ` JD Smith [this message]
2021-04-25 17:34 ` Lars Ingebrigtsen
2021-04-25 17:53 ` JD Smith
2021-04-25 19:19 ` Lars Ingebrigtsen
2021-10-13 16:45 ` Lars Ingebrigtsen
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=1971BD45-05FC-4124-8A3C-7EBC968D55D5@gmail.com \
--to=jdtsmith@gmail.com \
--cc=47657@debbugs.gnu.org \
--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).