From: Dan Nicolaescu <dann@ics.uci.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Chong Yidong <cyd@stupidchicken.com>,
2825@emacsbugs.donarmstrong.com, emacs-devel@gnu.org
Subject: bug#2825: 23.0.91; initial-buffer-choice useless with emacs daemon
Date: Sat, 11 Apr 2009 16:34:58 -0700 (PDT) [thread overview]
Message-ID: <200904112334.n3BNYwuE019572__34264.3013493673$1239494762$gmane$org@godzilla.ics.uci.edu> (raw)
In-Reply-To: <jwvk55ryram.fsf-monnier+emacsbugreports__39011.3984387883$1239475844$gmane$org@gnu.org> (Stefan Monnier's message of "Sat, 11 Apr 2009 14:34:56 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> >> > the new variable initial-buffer-choice seems useless when using emacs
> >> > as a daemon and emacsclient. This variable probably sets the initial
> >> > frame of the daemon, but does not affect the emacs clients. The buffer
> >> > is opened but not visible, the *scratch* buffer is opened instead.
> >>
> >> Currently, server-create-tty-frame and server-create-window-system-frame
> >> are hardcoded to display *scratch* if no emacsclient argument is given.
> >> In bug #2825, Damien Cassou has argued that they should obey
> >> initial-buffer-choice.
> >>
> >> Are there any objections?
>
> > Showing the startup screen every time when connecting to the server can
> > be seriously annoying for the user.
>
> I'm not sure what you mean by "the startup screen", but if a user
> prefers to start with a (dired "~/") than with *scratch*, I can't think
> of a good reason why we should disregard this preference when connecting
> via the emacsclient.
The startup screen is what `display-startup-screen' displays.
And that's my point too, *scratch* is a fine choice for now.
next prev parent reply other threads:[~2009-04-11 23:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ocv5mei7.fsf@cyd.mit.edu>
2009-04-11 15:13 ` bug#2825: 23.0.91; initial-buffer-choice useless with emacs daemon Dan Nicolaescu
[not found] ` <200904111513.n3BFD6fp012593@godzilla.ics.uci.edu>
2009-04-11 18:34 ` Stefan Monnier
2009-04-11 23:34 ` Dan Nicolaescu [this message]
[not found] ` <200904112334.n3BNYwuE019572@godzilla.ics.uci.edu>
2009-04-13 17:51 ` Stefan Monnier
2009-04-13 18:13 ` Dan Nicolaescu
[not found] ` <200904131813.n3DIDinI026826@godzilla.ics.uci.edu>
2009-04-14 2:07 ` Stefan Monnier
2009-04-14 2:35 ` Dan Nicolaescu
[not found] ` <200904140235.n3E2Zp0J008505@godzilla.ics.uci.edu>
2009-04-14 3:49 ` Stefan Monnier
2009-04-10 2:25 Chong Yidong
-- strict thread matches above, loose matches on Subject: below --
2009-03-30 13:57 Damien Cassou
2012-04-20 10:05 ` Chong Yidong
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='200904112334.n3BNYwuE019572__34264.3013493673$1239494762$gmane$org@godzilla.ics.uci.edu' \
--to=dann@ics.uci.edu \
--cc=2825@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).