From: Doug Davis <ddavis@ddavis.io>
To: 45679@debbugs.gnu.org
Subject: bug#45679: 28.0.50; python-mode variable font locking is inconsistent
Date: Wed, 13 Jan 2021 12:44:37 -0500 [thread overview]
Message-ID: <m2a6tczq7u.fsf@ddavis.io> (raw)
In-Reply-To: <m2czyj9e9p.fsf@ddavis.io> (Doug Davis's message of "Tue, 05 Jan 2021 17:04:34 -0600")
Doug Davis <ddavis@ddavis.io> writes:
> My guess is b2ce94fa5e introduced the bug.
My first guess was wrong. I tested python.el after a few commits over
the last few months and it was after 296e4dd and e7b4f46 where the bug
pops up.
next prev parent reply other threads:[~2021-01-13 17:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 21:07 bug#45679: 28.0.50; python-mode variable font locking is inconsistent Doug Davis
2021-01-05 22:51 ` Doug Davis
2021-01-05 23:04 ` Doug Davis
2021-01-13 17:44 ` Doug Davis [this message]
2021-03-01 0:47 ` Doug Davis
2021-03-01 0:55 ` Doug Davis
2021-03-01 1:03 ` Doug Davis
2022-05-16 13:42 ` 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=m2a6tczq7u.fsf@ddavis.io \
--to=ddavis@ddavis.io \
--cc=45679@debbugs.gnu.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).