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

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