Subject: bug#17046: 24.3.50; On startup emacs frame has no minibuffer or windows decorations

From: Robert Marshall <[email-masked]>
Date: Sun, 23 Mar 2014 21:01:16 +0000

Juanma Barranquero writes:
 > On Sun, Mar 23, 2014 at 8:32 PM, Robert Marshall <[email-masked]> wrote:
 > 
 > > However if I comment out the (display line but *leave in* the
 > > :force-display t parameter - the bug is still present - so in this case
 > > :force-display provokes the bug - it would have been ok without that
 > > line.
 > 
 > Please try this:
 > 
 > - edit lisp/frameset.el, and in line 1149, change
 > 
 >    (eq (frame-parameter nil 'display)
 > 
 > to
 > 
 >    (equal (frame-parameter nil 'display)
 > 
=== modified file 'lisp/frameset.el'
*** lisp/frameset.el	2014-03-12 18:36:26 +0000
--- lisp/frameset.el	2014-03-23 20:51:56 +0000
***************
*** 1146,1152 ****
  		     frame to-tty duplicate)
  		;; Only set target if forcing displays and the target display is different.
  		(unless (or (frameset-keep-original-display-p force-display)
! 			    (eq (frame-parameter nil 'display)
  				(cdr (assq 'display frame-cfg))))
  		  (setq frameset--target-display (cons 'display
  						       (frame-parameter nil 'display))
--- 1146,1152 ----
  		     frame to-tty duplicate)
  		;; Only set target if forcing displays and the target display is different.
  		(unless (or (frameset-keep-original-display-p force-display)
! 			    (equal (frame-parameter nil 'display)
  				(cdr (assq 'display frame-cfg))))
  		  (setq frameset--target-display (cons 'display
  						       (frame-parameter nil 'display))

 > save, compile frameset.el, and try again.
 > 

and saved and compiled but the bug is still present (tried with both
the display parameter and :force-display - uncommenting them separately).
So I can't see any change in behaviour.

Robert
-- 
Robert Marshall