bug#879: marked as done (23.0.60; startup warning & redisplay noisy)

[Emacs bug Tracking System]

Your message dated Sat, 20 Dec 2008 16:26:36 +0800
with message-id <494CAC3C.4030208@f2s.com>
and subject line Re: 23.0.60; startup warning & redisplay noisy
has caused the Emacs bug report #879,
regarding 23.0.60; startup warning & redisplay noisy
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
879: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=879
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

--- Begin Message --- Subject: 23.0.60; startup warning & redisplay noisy Date: Thu, 4 Sep 2008 10:29:59 +0800

     Two bugs:
     1. ntemacs will show the following warning message when starting up.
           Emergency (alloc): Warning: past 85% of memory limit

      2. There are lots of noisy points on the screen when you trigger Ctrl-H i. (screenshot
      attached).
           I have tried font: Consolas, Monaco. It's much more noticeable if you are using
        Monaco(http://www.gringod.com/wp-upload/MONACO.TTF).
       
      Best wishes
                                                                                        Kevin

noisy1.png
Description: PNG image

noisy2.png
Description: PNG image

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: 23.0.60; startup warning & redisplay noisy
>
>
>
>
> Date: 
>
> Sat, 20 Dec 2008 16:26:36 +0800
>
>
>
>
> User-agent: 
>
> Thunderbird 2.0.0.18 (Windows/20081105)
>
>
>
>
> The redisplay bug was fixed by the change made to w32font.c on 2008-11-26.
>
> Thanks for reporting it.
>
> The memory warning was likely a temporary problem fixed by the 
> 2008-11-14 increase of puresize, or by running configure and bootstrap 
> again. Please let us know if it is still there.
>
>
> --- End Message ---