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

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 2825 in the body.
You can then email your comments to 2825 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Damien Cassou <damien.cassou <at> gmail.com>
To: emacs-pretest-bug <at> gnu.org
Subject: 23.0.91; initial-buffer-choice useless with emacs daemon
Date: Mon, 30 Mar 2009 15:57:59 +0200

Hi,

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.

Thank you

-- 
Damien Cassou
http://damiencassou.seasidehosting.st

Message #10 received at 2825 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Chong Yidong <cyd <at> stupidchicken.com>
To: emacs-devel <at> gnu.org
Cc: 2825 <at> debbugs.gnu.org
Subject: Re: 23.0.91; initial-buffer-choice useless with emacs daemon
Date: Thu, 09 Apr 2009 22:25:20 -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?

Message #13 received at 2825 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Dan Nicolaescu <dann <at> ics.uci.edu>
To: Chong Yidong <cyd <at> stupidchicken.com>
Cc: emacs-devel <at> gnu.org, 2825 <at> debbugs.gnu.org
Subject: Re: 23.0.91; initial-buffer-choice useless with emacs daemon
Date: Sat, 11 Apr 2009 08:13:06 -0700 (PDT)

Chong Yidong <cyd <at> stupidchicken.com> 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.

This situation is not equivalent with showing the startup screen when
starting emacs because we assume that emacs is not started very often.
Connecting/disconnecting to the server is a much more frequent action
for some use cases.

So changing this at this point does not sound like a good idea.  If it
needs to be changed at all it can wait until 23.2.  If many people don't
like it we'll generate yet another very long discussion (like all
discussions about the startup screen), and it's simply not worth it when
trying to get a release out.

Message #18 received at 2825 <at> emacsbugs.donarmstrong.com (full text, mbox):

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: Re: 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

Message #21 received at 2825 <at> emacsbugs.donarmstrong.com (full text, mbox):

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

Stefan Monnier <monnier <at> 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.

Message #26 received at 2825 <at> emacsbugs.donarmstrong.com (full text, mbox):

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

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

What does this have to do with the question at hand.  IIUC th question
at hand is: why should the server.el code show "*scratch*" when the user
has set initial-buffer-choice to some file name?


        Stefan

Message #29 received at 2825 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Dan Nicolaescu <dann <at> ics.uci.edu>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 2825 <at> debbugs.gnu.org, Chong Yidong <cyd <at> stupidchicken.com>,
        emacs-devel <at> gnu.org
Subject: Re: bug#2825: 23.0.91; initial-buffer-choice useless with emacs daemon
Date: Mon, 13 Apr 2009 11:13:44 -0700 (PDT)

Stefan Monnier <monnier <at> iro.umontreal.ca> writes:

  > >> 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.
  > 
  > What does this have to do with the question at hand.  IIUC th question
  > at hand is: why should the server.el code show "*scratch*" when the user
  > has set initial-buffer-choice to some file name?

NEWS says:

** New user option `initial-buffer-choice' specifies what to display
after starting Emacs: startup screen, *scratch* buffer, visiting a
file or directory.

if the code is changed so that emacsclient called with no arguments
displays the startup screen __by default__, then we might have yet
another long discussion if this is the right thing to do.

Message #34 received at 2825 <at> emacsbugs.donarmstrong.com (full text, mbox):

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

>> >> 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.
>> 
>> What does this have to do with the question at hand.  IIUC th question
>> at hand is: why should the server.el code show "*scratch*" when the user
>> has set initial-buffer-choice to some file name?

> NEWS says:

> ** New user option `initial-buffer-choice' specifies what to display
> after starting Emacs: startup screen, *scratch* buffer, visiting a
> file or directory.

> if the code is changed so that emacsclient called with no arguments
> displays the startup screen __by default__, then we might have yet
> another long discussion if this is the right thing to do.

I do not understand what you mean.


        Stefan

Message #37 received at 2825 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Dan Nicolaescu <dann <at> ics.uci.edu>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 2825 <at> debbugs.gnu.org, Chong Yidong <cyd <at> stupidchicken.com>,
        emacs-devel <at> gnu.org
Subject: Re: bug#2825: 23.0.91; initial-buffer-choice useless with emacs daemon
Date: Mon, 13 Apr 2009 19:35:51 -0700 (PDT)

Stefan Monnier <monnier <at> iro.umontreal.ca> writes:

  > >> >> 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.
  > >> 
  > >> What does this have to do with the question at hand.  IIUC th question
  > >> at hand is: why should the server.el code show "*scratch*" when the user
  > >> has set initial-buffer-choice to some file name?
  > 
  > > NEWS says:
  > 
  > > ** New user option `initial-buffer-choice' specifies what to display
  > > after starting Emacs: startup screen, *scratch* buffer, visiting a
  > > file or directory.
  > 
  > > if the code is changed so that emacsclient called with no arguments
  > > displays the startup screen __by default__, then we might have yet
  > > another long discussion if this is the right thing to do.
  > 
  > I do not understand what you mean.

Currently:
emacs -q -f server-start

emacsclient -t
shows the *scratch* buffer.

Will the proposed change will make
emacsclient -t
show the startup screen?

If yes, then IMO it's not a good idea to implement such a change of
behavior at this time.

Message #42 received at 2825 <at> emacsbugs.donarmstrong.com (full text, mbox):

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

> Will the proposed change will make
> emacsclient -t
> show the startup screen?

Of course not.  We're only talking about the case where "the user
has set initial-buffer-choice to some file name".


        Stefan

Message #47 received at 2825 <at> debbugs.gnu.org (full text, mbox):

From: Chong Yidong <cyd <at> gnu.org>
To: Damien Cassou <damien.cassou <at> gmail.com>
Cc: 2825 <at> debbugs.gnu.org
Subject: Re: bug#2825: 23.0.91; initial-buffer-choice useless with emacs daemon
Date: Fri, 20 Apr 2012 18:05:40 +0800

Damien Cassou <damien.cassou <at> gmail.com> 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.

I've changed the trunk to reflect this behavior.  Thanks.

Previous Next

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