From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Erik Allik <eallik@gmail.com>
Cc: 11721-done@debbugs.gnu.org
Subject: bug#11721: 24.1; Rendering bug in 24.x on OS X
Date: Thu, 13 Sep 2012 13:16:01 +0200 [thread overview]
Message-ID: <9CBD9AB7-AA52-4BF5-8D9E-4B0CD671DAEC@swipnet.se> (raw)
In-Reply-To: <7E4C3B3B-0AAC-40C5-860C-8AA28E7576DB@gmail.com>
Hello.
13 sep 2012 kl. 08:11 skrev Erik Allik <eallik@gmail.com>:
> My 24.2 has been running without this bug since Sept 10 now. So I assume it can be considered as resolved :)
>
Okay, closing this bug.
Thanks!
Jan D.
> Erik
>
>
> On 2012.09.10, at 19:59, Jan Djärv wrote:
>
>> Hello.
>>
>> 10 sep 2012 kl. 17:14 skrev Erik Allik <eallik@gmail.com>:
>>
>>> I have just installed 24.2 for a starter; if it still has the bug, I'll try the latest trunk. Last time I only tried up to 24.1 IIRC. The problem is also that the bug doesn't seem to appear on the first run, so I might possibly have to wait a couple of days to report back to you.
>>>
>>
>> No hurry, thanks for testing,
>>
>> Jan D.
>>
>>> Erik
>>>
>>>
>>> On 2012.09.10, at 18:00, Jan Djärv wrote:
>>>
>>>> Hello.
>>>>
>>>>> starting from 24.0.96, I'm experiencing serious rendering issues when
>>>>> scrolling text. When the text moves downwards, it "grabs" pixels of the
>>>>> window title bar, so a part of the text in the buffer becomes
>>>>> unreadable, until it is selected again, which re-renders it.
>>>>>
>>>>>
>>>>
>>>> A fix for bug 12088 might solve this also. Do you still see this behaviour in an up-to-date trunk?
>>>>
>>>> Jan D.
>>>>
>>
prev parent reply other threads:[~2012-09-13 11:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 19:40 bug#11721: 24.1; Rendering bug in 24.x on OS X Erik Allik
2012-07-02 1:26 ` Tim Blackman
2012-09-10 15:00 ` Jan Djärv
2012-09-10 15:14 ` Erik Allik
2012-09-10 16:59 ` Jan Djärv
2012-09-13 6:11 ` Erik Allik
2012-09-13 11:16 ` Jan Djärv [this message]
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=9CBD9AB7-AA52-4BF5-8D9E-4B0CD671DAEC@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=11721-done@debbugs.gnu.org \
--cc=eallik@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.