From: Eli Zaretskii <eliz@gnu.org>
To: Dale Sedivec <dale@codefu.org>
Cc: 33864@debbugs.gnu.org
Subject: bug#33864: 27.0.50; Display corruption with "small" font size when something is in the fringe
Date: Tue, 25 Dec 2018 15:33:42 +0200 [thread overview]
Message-ID: <83h8f191e1.fsf@gnu.org> (raw)
In-Reply-To: <CAEj9N4KT65T8KXCc2MSt5=bvXKDZ+PwpGfNnx3frdDhN+_dZBg@mail.gmail.com> (message from Dale Sedivec on Tue, 25 Dec 2018 00:01:58 -0600)
> From: Dale Sedivec <dale@codefu.org>
> Date: Tue, 25 Dec 2018 00:01:58 -0600
>
> Using Emacs master with the NeXTStep interface on macOS, I get display corruption on lines where features
> such as Flymake, Flycheck, or diff-hl display something in the fringe. This is a bit hard to describe, so I'm
> attaching a screen shot, and I've also made a short movie of this happening:
>
> https://www.dropbox.com/s/h9eqixqxst4wg37/emacs_27_small_font_fringe_problem.mp4?dl=0
Looks like the cursor's line is being cleared without telling Emacs
about that.
Does it help to decrease the size of the Flymake's fringe indicators
when you switch to a smaller font? From the screenshot it looks like
the indicator keeps its original size although the font becomes a lot
smaller.
next prev parent reply other threads:[~2018-12-25 13:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-25 6:01 bug#33864: 27.0.50; Display corruption with "small" font size when something is in the fringe Dale Sedivec
2018-12-25 13:33 ` Eli Zaretskii [this message]
2018-12-25 18:30 ` Dale Sedivec
2018-12-25 18:39 ` Eli Zaretskii
2018-12-25 19:06 ` Dale Sedivec
2018-12-25 19:16 ` Eli Zaretskii
2018-12-30 12:25 ` Robert Pluim
2018-12-30 15:26 ` Eli Zaretskii
[not found] ` <handler.33864.B.154571777811440.ack@debbugs.gnu.org>
2018-12-27 4:34 ` bug#33864: Acknowledgement (27.0.50; Display corruption with "small" font size when something is in the fringe) Dale Sedivec
2018-12-27 11:59 ` Alan Third
2018-12-27 15:45 ` Dale Sedivec
2018-12-27 16:30 ` Alan Third
2018-12-27 17:07 ` Dale Sedivec
2018-12-28 21:43 ` Alan Third
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=83h8f191e1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33864@debbugs.gnu.org \
--cc=dale@codefu.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 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.