On Feb 5, 2009, at 9:46 AM, Dan Nicolaescu wrote:

> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> It appears that setting initial-frame-alist has no effect if Emacs is
>> started with --daemon; is this intended?  Here's a case in point:
>>  ...
>> the resulting frame has default width and height, not those  
>> specified in
>> ~/.emacs.  But this would be expected if the initial frame is the  
>> one in
>> the xterm.  Whereas with --daemon, the apparent initial frame is  
>> the one
>> produced by emacsclient -c.
>
> It's not, the initial frame is a special frame that cannot be  
> displayed.
> Again: emacs --daemon is equivalent to emacs -nw -f server-start
> If you try more, you can probably find even more variations of this  
> same
> basic issue...
>
>> So is this a bug or expected behavior?  If the latter, shouldn't it
>> be documented?  (I hope it's relatively easily fixed bug, since I
>> would like to have setting initial-frame-alist take effect if Emacs
>> is started with --daemon.)
>
> Patches are welcome!

Is there a reason not to use `default-frame-alist' instead?