GNU bug report logs -
#18347
24.3.93; Incomplete splash screen display on Cygwin-w32 build
Previous Next
Reported by: Ken Brown <kbrown <at> cornell.edu>
Date: Thu, 28 Aug 2014 21:52:02 UTC
Severity: normal
Found in version 24.3.93
Fixed in version 24.3.94
Done: Ken Brown <kbrown <at> cornell.edu>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Fri, 29 Aug 2014 18:17:18 -0400
with message-id <5400FBEE.8090705 <at> cornell.edu>
and subject line Re: bug#18347: 24.3.93; Incomplete splash screen display on Cygwin-w32 build
has caused the debbugs.gnu.org bug report #18347,
regarding 24.3.93; Incomplete splash screen display on Cygwin-w32 build
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
18347: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18347
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
When I start up the Cygwin-w32 build of emacs, the image at the top of
the splash screen often fails to display. The following patch fixes it:
=== modified file 'lisp/startup.el'
--- lisp/startup.el 2014-07-08 09:17:09 +0000
+++ lisp/startup.el 2014-08-28 20:07:20 +0000
@@ -1812,7 +1812,7 @@
(let (chosen-frame)
;; MS-Windows needs this to have a chance to make the initial
;; frame visible.
- (if (eq system-type 'windows-nt)
+ (if (eq window-system 'w32)
(sit-for 0 t))
(dolist (frame (append (frame-list) (list (selected-frame))))
(if (and (frame-visible-p frame)
Is this still OK for the native Windows build? If so, is it OK to
install it in the release branch?
In GNU Emacs 24.3.93.2 (x86_64-unknown-cygwin)
of 2014-08-28 on moufang
Repository revision: 117464 rgm <at> gnu.org-20140828191824-o5hn2x503w527yhn
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --with-w32 --enable-checking=yes,glyphs 'CFLAGS=-g3 -O0''
[Message part 3 (message/rfc822, inline)]
Version: 24.3.94
> Basically, since creating a frame on w32 takes some time until the OS
> sets up the message pump for the new frame, Lisp code that creates a
> frame and immediately proceeds with manipulating the new frame might
> sometimes need sit-for to let the dust settle.
So it seems that the current bug probably has the same cause as
bug#16014. I've installed the fix (but using the window-system
function) in the release branch as bzr revision 117465.
Ken
This bug report was last modified 10 years and 263 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.