From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Yes, please allow pre-configuration of first frame [was: Blink Cursor mode is off by default] Date: Sat, 16 Jun 2018 20:26:29 +0300 Message-ID: <8336xmzlq2.fsf@gnu.org> References: <838t7lqnf0.fsf@gnu.org> <83zi01p6th.fsf@gnu.org> <13a2189b89d06be494cbc21561713d5d.squirrel@dancol.org> <83o9ggpwfs.fsf@gnu.org> <98930BC3-F62C-4BFF-8B06-8CFB65E8D243@gnu.org> <5659356aea4cdccd07e28e441c1ae98b.squirrel@dancol.org> <871sd8kugv.fsf_-_@moondust.localdomain> <5cc07aef-9c8b-4a5b-8cdb-3d003bed7151@dancol.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1529169889 23438 195.159.176.226 (16 Jun 2018 17:24:49 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 16 Jun 2018 17:24:49 +0000 (UTC) Cc: dancol@dancol.org, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jun 16 19:24:45 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fUEwO-0005yD-Mx for ged-emacs-devel@m.gmane.org; Sat, 16 Jun 2018 19:24:44 +0200 Original-Received: from localhost ([::1]:52301 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fUEyV-0005Wm-Mu for ged-emacs-devel@m.gmane.org; Sat, 16 Jun 2018 13:26:55 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55293) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fUEyI-0005Vg-2e for emacs-devel@gnu.org; Sat, 16 Jun 2018 13:26:44 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fUEyE-0005Ep-T5 for emacs-devel@gnu.org; Sat, 16 Jun 2018 13:26:41 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:39114) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fUEyE-0005Ed-Oz; Sat, 16 Jun 2018 13:26:38 -0400 Original-Received: from [176.228.60.248] (port=4135 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fUEyE-00040c-4I; Sat, 16 Jun 2018 13:26:38 -0400 In-reply-to: (message from Stefan Monnier on Sat, 16 Jun 2018 13:20:21 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:226382 Archived-At: > From: Stefan Monnier > Date: Sat, 16 Jun 2018 13:20:21 -0400 > Cc: emacs-devel@gnu.org > > > The file could just run against a dummy frame that happens to look like the > > GUI frame we'll eventually create. > > To reduce the breakage, the frame had batter be as real as possible > (e.g. plain normal frame, just `invisible`), but still: what will happen > when the .emacs code ends up prompting the user in the minibuffer? What if we create and display a small special frame, "normal" enough to support everything any .emacs could expect, but devoid of stuff like the menu bar, the tool bar, and the scroll bars? Many applications show something like that at startup, so I think that would look "professional" enough.