Subject: bug#5378: closed (Re: arbitrary user parameters in default-frame-alist not set in subsequent frames)

From: [email-masked] (GNU bug Tracking System)
Date: Thu, 01 Jul 2010 00:18:01 +0000

Your bug report

#5378: arbitrary user parameters in default-frame-alist not set in  subsequent frames

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
5378: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=5378
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: arbitrary user parameters in default-frame-alist not set in subsequent frames
From: Chong Yidong <[email-masked]>
To: Juanma Barranquero <[email-masked]>
Cc: [email-masked]
Date: Wed, 30 Jun 2010 20:17:19 -0400
List-Id: <debbugs-submit.debbugs.gnu.org>

> emacs -Q --eval "(add-to-list 'default-frame-alist '(my-parameter . t))"
> M-: (frame-parameter nil 'my-parameter)   =>   t
> C-x 5 2
> M-: (frame-parameter nil 'my-parameter)   =>   nil

I have checked in a fix that tweaks the way default-frame-alist is
handled during frame creation.  It should solve this problem.

Subject: arbitrary user parameters in default-frame-alist not set in subsequent frames
From: Juanma Barranquero <[email-masked]>
To: Bug-Gnu-Emacs <[email-masked]>
Date: Thu, 14 Jan 2010 15:43:35 +0100
List-Id: <debbugs-submit.debbugs.gnu.org>

---------- Forwarded message ----------
From: Juanma Barranquero <[email-masked]>
Date: Sun, Jan 3, 2010 at 00:35
Subject: Is this a bug? (arbitrary user parameters in
default-frame-alist not set in subsequent frames)
To: Emacs developers <[email-masked]>

I'll file a bug report, assuming it is unexpected.

 emacs -Q --eval "(add-to-list 'default-frame-alist '(my-parameter . t))"
 M-: (frame-parameter nil 'my-parameter)   =>   t
 C-x 5 2
 M-: (frame-parameter nil 'my-parameter)   =>   nil

This happens for user-defined frame parameters; for example, if you
set `background-color' it is correctly passed.

Are initial-frame-alist and default-frame-alist intended for
"meaningful" stuff (X resources and other things that can affect frame
creation) only, or should user values be honored too?

   Juanma