From: Eli Zaretskii <eliz@gnu.org>
To: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
Cc: 36030@debbugs.gnu.org
Subject: bug#36030: Changing the region or the point changes the way characters are displayed
Date: Thu, 06 Jun 2019 17:18:53 +0300 [thread overview]
Message-ID: <831s06ssoi.fsf@gnu.org> (raw)
In-Reply-To: <3411e468-633a-f643-1cc7-58ffce2483ee@gmail.com> (message from Clément Pit-Claudel on Fri, 31 May 2019 16:51:10 -0400)
> Cc: 36030@debbugs.gnu.org
> From: Clément Pit-Claudel <cpitclaudel@gmail.com>
> Date: Fri, 31 May 2019 16:51:10 -0400
>
> > I see none of that in "emacs -Q". I also don't understand how
> > resizing the frame could cause these effects. If the recipe is more
> > complicated than just copy/paste the strings you show into *scratch*,
> > please be sure to show the whole recipe. E.g., where did the face
> > properties come from?
>
> This is python-mode's syntax highlighting. Unfortunately, I don't have a reproducible recipe for these issues yet; they happen on my machine, but I have many custom fonts and Emacs customization here. I will try to find a recipe.
Could you please try the latest master and see if these problems are
solved? If not, could you please try applying the patch I posted in
bug#28312, and see if that fixes your problems?
Thanks.
next prev parent reply other threads:[~2019-06-06 14:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 15:21 bug#36030: Changing the region or the point changes the way characters are displayed Clément Pit-Claudel
2019-05-31 15:36 ` Eli Zaretskii
2019-05-31 17:06 ` Clément Pit-Claudel
2019-05-31 19:02 ` Eli Zaretskii
2019-05-31 19:28 ` Clément Pit-Claudel
2019-05-31 20:02 ` Eli Zaretskii
2019-05-31 20:51 ` Clément Pit-Claudel
2019-06-01 6:22 ` Eli Zaretskii
2019-06-06 14:18 ` Eli Zaretskii [this message]
2019-06-07 17:45 ` Clément Pit-Claudel
2019-06-07 19:50 ` Eli Zaretskii
2019-06-07 21:11 ` Clément Pit-Claudel
2019-06-08 5:54 ` Eli Zaretskii
2019-06-10 20:32 ` Clément Pit-Claudel
2019-06-11 2:27 ` Eli Zaretskii
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=831s06ssoi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36030@debbugs.gnu.org \
--cc=cpitclaudel@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.