unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: Jeff Spencer <jeffspencerd@gmail.com>,
	51362@debbugs.gnu.org,
	Dario Gjorgjevski <dario.gjorgjevski@gmail.com>
Subject: bug#51362: python font-lock-mode in emacs 28 seems broken
Date: Sun, 31 Oct 2021 10:34:30 +0100	[thread overview]
Message-ID: <87bl35v8pl.fsf@gmail.com> (raw)
In-Reply-To: <CADwFkmmT_V58u-3HTX1Q9VV42Qs+-1pufMSdSEPX45PapOa6dg@mail.gmail.com> (Stefan Kangas's message of "Sun, 24 Oct 2021 05:45:38 -0700")

[-- Attachment #1: Type: text/plain, Size: 468 bytes --]

Stefan Kangas <stefan@marxist.se> writes:

> Do you have an example file or snippet where font-lock fails?

I've tried to come up with a minimal reproducer; see attached file, and
screenshots.  In Emacs 28, the second assignment is not fontified until
the user starts editing the buffer.

I glanced at python.el's font-lock rules and tried to revert recent
changes, but tripped over conflicts.  I'm speculatively CC'ing Dario, in
case the issue looks obvious to him?


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: repro.py --]
[-- Type: text/x-python, Size: 27 bytes --]

a = foo(x='a')
b = a.bar()

[-- Attachment #3: Screenshot_20211031_103332.png --]
[-- Type: image/png, Size: 132814 bytes --]

  parent reply	other threads:[~2021-10-31  9:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-23 20:06 bug#51362: python font-lock-mode in emacs 28 seems broken Jeff Spencer
2021-10-24 12:45 ` Stefan Kangas
2021-10-24 22:37   ` Jeff Spencer
2021-10-24 22:40     ` Jeff Spencer
2021-10-31  9:34   ` Kévin Le Gouguec [this message]
2021-11-11  8:04     ` Dario Gjorgjevski
2021-11-11  8:48       ` Stefan Kangas
2021-11-11 12:37       ` Lars Ingebrigtsen
2022-04-17 23:32 ` kobarity
2022-04-18  9:50   ` Lars Ingebrigtsen
2022-04-18 12:34     ` kobarity
2022-04-18 12:36       ` Lars Ingebrigtsen
2022-05-16 13:40         ` Lars Ingebrigtsen
2022-05-16 14:21           ` kobarity

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=87bl35v8pl.fsf@gmail.com \
    --to=kevin.legouguec@gmail.com \
    --cc=51362@debbugs.gnu.org \
    --cc=dario.gjorgjevski@gmail.com \
    --cc=jeffspencerd@gmail.com \
    --cc=stefan@marxist.se \
    /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).