[Emacs-bug-tracker] bug#5378: closed (arbitrary user parameters in default-frame-alist not set in subsequent frames)

[GNU bug Tracking System]

Your message dated Wed, 30 Jun 2010 20:17:19 -0400
with message-id <address@hidden>
and subject line Re: arbitrary user parameters in default-frame-alist not set 
in subsequent frames
has caused the GNU bug report #5378,
regarding arbitrary user parameters in default-frame-alist not set in  
subsequent frames
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
5378: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=5378
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> arbitrary user parameters in default-frame-alist not set in 	subsequent frames
>
>
>
>
> Date: 
>
> Thu, 14 Jan 2010 15:43:35 +0100
>
>
>
>
> ---------- Forwarded message ----------
> From: Juanma Barranquero <address@hidden>
> 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 <address@hidden>
>
>
> 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
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: arbitrary user parameters in default-frame-alist not set in	subsequent frames
>
>
>
>
> Date: 
>
> Wed, 30 Jun 2010 20:17:19 -0400
>
>
>
>
> > 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.
>
>
> --- End Message ---