From: Will Farrington <wcfarrington@gmail.com>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: Stephen Berman <stephen.berman@gmx.net>, emacs-devel@gnu.org
Subject: Re: initial-frame-alist
Date: Thu, 5 Feb 2009 10:13:02 -0500 [thread overview]
Message-ID: <CB07D352-92D3-4C75-B914-3F141A6798A3@gmail.com> (raw)
In-Reply-To: <200902051446.n15Ek525004594@rodan.ics.uci.edu>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
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?
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2427 bytes --]
next prev parent reply other threads:[~2009-02-05 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 11:24 initial-frame-alist Stephen Berman
2009-02-05 14:46 ` initial-frame-alist Dan Nicolaescu
2009-02-05 15:13 ` Will Farrington [this message]
2009-02-05 15:51 ` initial-frame-alist Stephen Berman
2009-02-05 16:13 ` initial-frame-alist mail
2009-02-05 23:19 ` initial-frame-alist Stephen Berman
2009-02-05 19:38 ` initial-frame-alist Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CB07D352-92D3-4C75-B914-3F141A6798A3@gmail.com \
--to=wcfarrington@gmail.com \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=stephen.berman@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).