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: Should this package be included into the NS port? Date: Wed, 23 May 2018 20:23:55 +0300 Message-ID: <838t8acml0.fsf@gnu.org> References: <20180515183631.GB27909@breton.holly.idiocy.org> <20180518193632.GA31241@breton.holly.idiocy.org> <20180519103329.GB31853@breton.holly.idiocy.org> <83k1rucs15.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1527096113 10617 195.159.176.226 (23 May 2018 17:21:53 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 23 May 2018 17:21:53 +0000 (UTC) Cc: alan@idiocy.org, nick@tenpoint.co.nz, georgedp@orbitalimpact.com, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed May 23 19:21:49 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 1fLXSM-0002eL-Hn for ged-emacs-devel@m.gmane.org; Wed, 23 May 2018 19:21:46 +0200 Original-Received: from localhost ([::1]:34704 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fLXUT-0002Zl-IN for ged-emacs-devel@m.gmane.org; Wed, 23 May 2018 13:23:57 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39120) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fLXUM-0002ZV-LO for emacs-devel@gnu.org; Wed, 23 May 2018 13:23:51 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fLXUI-0004rt-Lq for emacs-devel@gnu.org; Wed, 23 May 2018 13:23:50 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:45610) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fLXUI-0004qY-IR; Wed, 23 May 2018 13:23:46 -0400 Original-Received: from [176.228.60.248] (port=2571 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fLXUI-0004ph-04; Wed, 23 May 2018 13:23:46 -0400 In-reply-to: (message from Stefan Monnier on Wed, 23 May 2018 12:37:39 -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:225616 Archived-At: > From: Stefan Monnier > Date: Wed, 23 May 2018 12:37:39 -0400 > Cc: alan@idiocy.org, Nick Helm , > georgedp@orbitalimpact.com, emacs-devel@gnu.org > > >> And, I guess, how does emacsclient beat this one-frame-must-exist > >> limitation – does it maintain some kind of fake frame that it hides from > >> the windowing system? > > That's exactly why your notion of frame-centric Emacs is inaccurate. > > IIRC, the emacs daemon solves this by using the "initial-frame" which is > associated to the "stdio terminal" (the special frame and terminal also > used in batch mode). Yes, but if you count that as a frame, then the one-frame-must-exist limitation is meaningless, because that frame always exists, it comes from the time Emacs was dumped.