From: Stephen Berman <stephen.berman@gmx.net>
To: emacs-devel@gnu.org
Subject: initial-frame-alist
Date: Thu, 05 Feb 2009 12:24:10 +0100 [thread overview]
Message-ID: <87prhxazz9.fsf@escher.local.home> (raw)
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:
Let ~/.emacs consist of this sexp:
(setq initial-frame-alist
(append initial-frame-alist '((width . 85) (height . 58))))
Then do this:
$ emacs --daemon
$ emacsclient -c
The resulting frame has default width and height, not those specified in
~/.emacs. If instead I start Emacs like this:
$ emacs
then the resulting frame does width 85 and height 58.
I note that after starting Emacs like this:
$ emacs -nw -f server-start
and then in another xterm typing:
$ emacsclient -c
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. 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.)
Steve Berman
next reply other threads:[~2009-02-05 11:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 11:24 Stephen Berman [this message]
2009-02-05 14:46 ` initial-frame-alist Dan Nicolaescu
2009-02-05 15:13 ` initial-frame-alist Will Farrington
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
-- strict thread matches above, loose matches on Subject: below --
2009-12-26 15:15 initial-frame-alist Julianne
2009-12-28 0:02 ` initial-frame-alist Peter Dyballa
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87prhxazz9.fsf@escher.local.home \
--to=stephen.berman@gmx.net \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.