From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: GUI vs TTY when saving & restoring framesets Date: Mon, 23 Jan 2017 11:16:42 -0500 Message-ID: References: <834m0r5aiu.fsf@gnu.org> <83d1fe4fcq.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1485188269 19226 195.159.176.226 (23 Jan 2017 16:17:49 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 23 Jan 2017 16:17:49 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 23 17:17:42 2017 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 1cVhJ6-0002w2-S7 for ged-emacs-devel@m.gmane.org; Mon, 23 Jan 2017 17:17:25 +0100 Original-Received: from localhost ([::1]:42951 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cVhJA-00025N-4V for ged-emacs-devel@m.gmane.org; Mon, 23 Jan 2017 11:17:28 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41725) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cVhJ1-00025H-Qj for emacs-devel@gnu.org; Mon, 23 Jan 2017 11:17:20 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cVhIx-0003C0-S5 for emacs-devel@gnu.org; Mon, 23 Jan 2017 11:17:19 -0500 Original-Received: from [195.159.176.226] (port=49617 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cVhIx-0003B5-L8 for emacs-devel@gnu.org; Mon, 23 Jan 2017 11:17:15 -0500 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1cVhIZ-0000jX-NG for emacs-devel@gnu.org; Mon, 23 Jan 2017 17:16:51 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 34 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:0sGI0mQJixtuKmuMx+cTGBsITrc= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 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:211579 Archived-At: > It wasn't the intention. OTOH, as a -nw session on GNU/Linux can have both > GUI and tty frames, I'm not sure it is a bug, just we're entering > unspecified territory. I mean, what if the user creates a GUI frame from a > -nw session, and then exits and reenters Emacs in -nw mode. Shouldn't the > GUI frame be restored too? We haven't decided (likely because the issue > didn't present itself earlier than that bug report) how to deal when > running mixed frames' instances. I think this is basically the same issue as "multiple X11 servers". IOW, the issue is how to handle frames on multiple "terminals" (in the sense of `frame-terminal`). I believe most users use Emacs in "single terminal" mode with very few exceptions, and even when they occasionally or often use a single Emacs session with frames on several terminals, they most likely don't want the "desktop save&restore" to pay attention to the frames on the "non-main terminal" because at startup those other terminals often don't exist or aren't accessible. There's also an issue of naming: the "main terminal" doesn't need to have a name (and in 99% of the cases shouldn't have a name: if I save an Emacs session in an environment where I had DISPLAY=:5, and try to restore it in an environment where DISPLAY=:4 it should use :4 rather than :5 to open my frames), whereas the other ones need to be named. > Thinking about these issues, I suddenly realized that, if we were to treat > -nw and GUI sessions as different (frameset-wise, I mean), we could just > save the GUI frameset and the -nw frameset as distinct entities in the > desktop file, and just restore the one appropriate. No mixing. Sounds like a good idea. Stefan