GNU bug report logs - #2825
23.0.91; initial-buffer-choice useless with emacs daemon

Previous Next

Package: emacs;

Reported by: Damien Cassou <damien.cassou <at> gmail.com>

Date: Mon, 30 Mar 2009 14:05:06 UTC

Severity: wishlist

Done: Chong Yidong <cyd <at> gnu.org>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Dan Nicolaescu <dann <at> ics.uci.edu>
Cc: Chong Yidong <cyd <at> stupidchicken.com>, 2825 <at> debbugs.gnu.org,
        emacs-devel <at> gnu.org
Subject: bug#2825: 23.0.91; initial-buffer-choice useless with emacs daemon
Date: Sat, 11 Apr 2009 14:34:56 -0400

>> > 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.


        Stefan
This bug report was last modified 13 years and 93 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.