From: Dale Sedivec <dale@codefu.org>
To: Eli Zaretskii <eliz@gnu.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 13:06:04 -0600 [thread overview]
Message-ID: <CAEj9N4Lc+O8Gmjk+UzTSoMFE8C8Faz1HYJ0c18pNp82kh+uteQ@mail.gmail.com> (raw)
In-Reply-To: <838t0d8n92.fsf@gnu.org>
On Tue, Dec 25, 2018 at 12:39 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Dale Sedivec <dale@codefu.org>
> > Date: Tue, 25 Dec 2018 12:30:01 -0600
> > Cc: 33864@debbugs.gnu.org
> >
> > > 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.
> >
> > I think I did what you ask by making a bitmap with just a single pixel
> > turned on:
> >
> > (define-fringe-bitmap 'smallest
> > (vector #b00000000
> > #b00000000
> > #b00000000
> > #b00000000
> > #b00000000
> > #b00000000
> > #b00000000
> > #b00000000
> > #b00010000
> > #b00000000
> > #b00000000
> > #b00000000
> > #b00000000
> > #b00000000
> > #b00000000
> > #b00000000
> > #b00000000))
> >
> > (setq flymake-note-bitmap '(smallest compilation-info))
[...]
> I think I meant to make the indicator bitmap smaller, i.e. have fewer
> members in the above vector. Since you switch to a size-9 font, which
> is 3/4 of the default size, how about making the above bitmap have 12
> or 13 lines, instead of 17 now?
I reduced the above vector to just 12 lines and the problem still
occurred, same with 10 lines. Reducing the bitmap to 9 lines,
however, DID FIX the problem. I saw no corruption on the line when
the bitmap was only 9 lines high.
To be clear, this was the 9 line bitmap that fixed the problem under
Menlo 9 pt font:
(define-fringe-bitmap 'smallest
(vector #b00000000
#b00000000
#b00000000
#b00010000
#b00000000
#b00000000
#b00000000
#b00000000
#b00000000))
(I didn't even realize I could reduce the height of the bitmap in this
way—sorry I misunderstood your original request, I have never used the
fringe APIs before.)
Dale
next prev parent reply other threads:[~2018-12-25 19:06 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
2018-12-25 18:30 ` Dale Sedivec
2018-12-25 18:39 ` Eli Zaretskii
2018-12-25 19:06 ` Dale Sedivec [this message]
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
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=CAEj9N4Lc+O8Gmjk+UzTSoMFE8C8Faz1HYJ0c18pNp82kh+uteQ@mail.gmail.com \
--to=dale@codefu.org \
--cc=33864@debbugs.gnu.org \
--cc=eliz@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).