From: Keith David Bershatsky <esq@lawlist.com>
To: Alan Third <alan@idiocy.org>
Cc: "36633@debbugs.gnu.org" <36633@debbugs.gnu.org>,
Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>,
Stefan Kangas <stefan@marxist.se>
Subject: bug#36633: Scrolling by pixels: visible stretch glyphs overwrite header-line.
Date: Wed, 17 Jul 2019 12:08:09 -0700 [thread overview]
Message-ID: <88C33FD0-4D74-4A96-A681-54FD938BE9F6@lawlist.com> (raw)
In-Reply-To: <20190717183131.GA75658@breton.holly.idiocy.org>
I misunderstood about the need to apply the patch and assumed the master branch already contained the fix. I will be at a computer later on today and will apply the patch and report back with the results.
On Jul 17, 2019, at 11:31 AM, Alan Third <alan@idiocy.org> wrote:
> On Tue, Jul 16, 2019 at 11:34:57PM -0700, Keith David Bershatsky wrote:
>> Thank you, Alan, for your work on issue 36633.
>>
>> Today, I built an Emacs master branch on OSX 10.6.8 using:
>>
>> Last Commit : Tue Jul 16 16:04:54 2019 -0700
>> : Glenn Morris <rgm@gnu.org>
>> : 7e70c78867ab2b8e280f6a087b32a947b13776a7
>> : An electric test is now passing
>
> Did you apply the patch in the email? It clears up all the flickering
> I could see here, so I’m a bit surprised to hear it did nothing at
> all.
> --
> Alan Third
next prev parent reply other threads:[~2019-07-17 19:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-13 2:10 bug#36633: Scrolling by pixels: visible stretch glyphs overwrite header-line Keith David Bershatsky
2019-07-13 6:19 ` Eli Zaretskii
2019-07-13 8:32 ` Stefan Kangas
2019-07-13 8:39 ` Eli Zaretskii
2019-07-14 10:39 ` Alan Third
2019-07-14 16:47 ` Keith David Bershatsky
2019-07-15 12:26 ` Tak Kunihiro
2019-07-16 20:38 ` Alan Third
2019-07-14 16:52 ` Keith David Bershatsky
2019-07-17 6:34 ` Keith David Bershatsky
2019-07-17 18:31 ` Alan Third
2019-07-17 19:08 ` Keith David Bershatsky [this message]
2019-07-17 23:31 ` Tak Kunihiro
2019-07-18 3:56 ` Keith David Bershatsky
2019-07-27 17:32 ` 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=88C33FD0-4D74-4A96-A681-54FD938BE9F6@lawlist.com \
--to=esq@lawlist.com \
--cc=36633@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=stefan@marxist.se \
--cc=tkk@misasa.okayama-u.ac.jp \
/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).