From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Sascha Wilde Newsgroups: gmane.emacs.devel Subject: New start up splash screen annoyance... Date: Sun, 09 Sep 2007 15:56:07 +0200 Message-ID: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1189348221 5565 80.91.229.12 (9 Sep 2007 14:30:21 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 9 Sep 2007 14:30:21 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 10 00:30:08 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1IUUjj-00033Q-4T for ged-emacs-devel@m.gmane.org; Sun, 09 Sep 2007 23:54:35 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IUNFM-0002H1-7H for ged-emacs-devel@m.gmane.org; Sun, 09 Sep 2007 09:54:44 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IUNFH-0002DM-Lf for emacs-devel@gnu.org; Sun, 09 Sep 2007 09:54:39 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IUNFF-0002C2-PR for emacs-devel@gnu.org; Sun, 09 Sep 2007 09:54:39 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IUNFF-0002Br-Lv for emacs-devel@gnu.org; Sun, 09 Sep 2007 09:54:37 -0400 Original-Received: from ns.km1136.keymachine.de ([62.141.58.119] helo=km1136.keymachine.de) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1IUNFF-00007g-3Q for emacs-devel@gnu.org; Sun, 09 Sep 2007 09:54:37 -0400 Original-Received: from kenny.sha-bang.de (xdslcf091.osnanet.de [89.166.133.91]) (authenticated bits=0) by km1136.keymachine.de (8.12.11.20060308/8.12.10) with ESMTP id l89DsTms007484 for ; Sun, 9 Sep 2007 15:54:30 +0200 Original-Received: from wilde by kenny.sha-bang.de with local (Kenny MUA v.0409034.42) ID 1IUNGh-0007YH-Fn for emacs-devel@gnu.org; Sun, 09 Sep 2007 15:56:07 +0200 User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/23.0.50 (gnu/linux) X-Detected-Kernel: Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:78318 Archived-At: Hi *, basically I like the idea of a configurable start-up behavior. But the current implementation is IMNSHO very flawed: - First and most annoying: starting Emacs with an file to visit as argument no longer works as expected. Without doing any configuration you always get the new splash screen and of cause C-l or starting editing doesn't make it go away. You can switch to the buffer with the file using C-x C-b, but the splash screen doesn't tell you that. I would like to have the old behavior back: if a file name was given on the command line the user definitely wants to edit that file, and so any editing/movement/redraw command should switch to that files buffer immediately. In case people don't agree on that, the splash screen should at least mention how to enter the buffer. - Second, and maybe even worse: None of the settings for initial-buffer-choice restores the old behavior. One might expect, that setting initial-buffer-choice to t (open *scratch* buffer) would be the right choice, but it isn't. If set that way, the annoying behavior described above stays with the only differences, that the *scratch* buffer is opened and stays, even if a file to edit was given on start-up. One would expect that at least one value of initial-buffer-choice would restore the old behavior, which many of use are used to and which at least me likes best: open *scratch* as default but open the buffer(s) for the given files from the command line if there were any. The only working solution is to set inhibit-splash-screen to t and leave initial-buffer-choice nil -- which is a pity as the new possibility of customizing the default behavior is lost. - Third, as setting inhibit-splash-screen is the only (and as far as I can see not ell documented) way to get back the old behavior, it is a (minor) annoyance that inhibit-splash-screen not only turns of the splash screen, but the initial message in the *scratch* buffer too. Actually I never understood why this two things are configured by only one variable. cheers sascha -- Sascha Wilde "Liebet eure Feinde, vielleicht schadet das ihrem Ruf" (Stanislaw Jerzy Lec)