emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-bug-tracker] bug#5748: marked as done (24.0.50; Gomoku startup la


From: GNU bug Tracking System
Subject: [Emacs-bug-tracker] bug#5748: marked as done (24.0.50; Gomoku startup latency)
Date: Mon, 22 Mar 2010 22:46:02 +0000

Your message dated Mon, 22 Mar 2010 23:45:08 +0100
with message-id <address@hidden>
and subject line Re: bug#5748: 24.0.50; Gomoku startup latency
has caused the GNU bug report #5748,
regarding 24.0.50; Gomoku startup latency
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 address@hidden
immediately.)


-- 
5748: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=5748
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 24.0.50; Gomoku startup latency Date: Sun, 21 Mar 2010 16:09:34 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux)
[I sent the following last Friday along with two other bug reports
involving Gomoku, but this one seems to have gotten lost, so I'm
resending it.]

1. Let ~/.emacs consist of this sexp:
(setq initial-frame-alist '((fullscreen . fullheight)))
2. Start Emacs with the above init file.
3. M-x gomoku
=> There is a noticeable delay loading the game -- on my system 3-4
seconds.  This also occurs when the height frame parameter is assigned a
corresponding integer value.  The latency decreases as the height value
decreases.  (At the default height of 35, the startup time is
practically instantaneous.)

In GNU Emacs 24.0.50.1 (i686-pc-linux-gnu, GTK+ Version 2.18.6)
 of 2010-03-19 on escher
Windowing system distributor `The X.Org Foundation', version 11.0.10605000
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: en_US.UTF-8
  value of $XMODIFIERS: @im=local
  locale-coding-system: utf-8-unix
  default enable-multibyte-characters: t




--- End Message ---
--- Begin Message --- Subject: Re: bug#5748: 24.0.50; Gomoku startup latency Date: Mon, 22 Mar 2010 23:45:08 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux)
On Mon, 22 Mar 2010 17:32:44 -0400 Glenn Morris <address@hidden> wrote:

> Stephen Berman wrote:
>
>> [I sent the following last Friday along with two other bug reports
>> involving Gomoku, but this one seems to have gotten lost, so I'm
>> resending it.]
>
> The original arrived as bug #5749. The headers seem to indicate it sat
> on "escher" for several days, so not our fault for once! :)

Yes, that's my home box, which does not stay up 24/7.  After I got
prompt acknowledgements of the other two reports on Friday, I checked
the mail log and saw this report was delayed due to my ISP.  Then I had
to shut down the machine and didn't reboot it till Sunday, and since the
report still hadn't arrived, I assumed it was lost and resent it.  To my
chagrin, shortly after getting the acknowledgement for the resent
report, the one for the original arrived :-( 
So I'll just close this duplicate.

Steve Berman


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]