From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.bugs Subject: bug#55070: 28.1; desktop-load doesn't work in -nw (non-gui) emacs Date: Tue, 26 Apr 2022 20:40:10 +0300 Organization: LINKOV.NET Message-ID: <86sfpzspz4.fsf@mail.linkov.net> References: <83fsm4pbs4.fsf@gnu.org> <6961B895-263C-4632-AA4E-8DE29D6160BC@swenson.org> <83sfq3op15.fsf@gnu.org> <86wnfcxnvf.fsf@mail.linkov.net> <87mtg8i1za.fsf@gnus.org> <86h76fu9q5.fsf@mail.linkov.net> <83r15jltce.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="722"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (x86_64-pc-linux-gnu) Cc: eric@swenson.org, 55070@debbugs.gnu.org, larsi@gnus.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Apr 26 19:43:14 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1njPDV-000AdY-To for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 26 Apr 2022 19:43:13 +0200 Original-Received: from localhost ([::1]:39794 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1njPDU-0002MB-Nu for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 26 Apr 2022 13:43:12 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35130) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1njPDK-0002LX-BE for bug-gnu-emacs@gnu.org; Tue, 26 Apr 2022 13:43:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:46573) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1njPDK-0006zY-2q for bug-gnu-emacs@gnu.org; Tue, 26 Apr 2022 13:43:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1njPDJ-0003So-VM for bug-gnu-emacs@gnu.org; Tue, 26 Apr 2022 13:43:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Juri Linkov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 26 Apr 2022 17:43:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 55070 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 55070-submit@debbugs.gnu.org id=B55070.165099493313246 (code B ref 55070); Tue, 26 Apr 2022 17:43:01 +0000 Original-Received: (at 55070) by debbugs.gnu.org; 26 Apr 2022 17:42:13 +0000 Original-Received: from localhost ([127.0.0.1]:40470 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1njPCX-0003RZ-Af for submit@debbugs.gnu.org; Tue, 26 Apr 2022 13:42:13 -0400 Original-Received: from relay11.mail.gandi.net ([217.70.178.231]:44129) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1njPCW-0003RM-22 for 55070@debbugs.gnu.org; Tue, 26 Apr 2022 13:42:12 -0400 Original-Received: (Authenticated sender: juri@linkov.net) by mail.gandi.net (Postfix) with ESMTPSA id 547A5100008; Tue, 26 Apr 2022 17:42:03 +0000 (UTC) In-Reply-To: <83r15jltce.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 26 Apr 2022 19:09:21 +0300") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:230747 Archived-At: >> ;; People don't expect emacs -nw, or --daemon, >> ;; to create graphical frames (bug#17693). >> ;; TODO perhaps there should be a separate value >> ;; for desktop-restore-frames to control this startup behavior? >> >> So this patch creates such separate values: > > Thanks, but I don't understand why you need the frameset part of the > patch. Because restoring frames on tty fails without this fix. > Or if you do need it, why does it have to look so ad-hoc? If > we want to support in frameset.el frames for which some frame > parameters make no sense, let's do that explicitly, not by sweeping > problems under the carpet by substituting some arbitrary values for > those parameters that give us trouble. These values are not arbitrary. The function frame-monitor-attributes used in the same fixed function frameset-move-onscreen returns on tty: ((geometry 0 0 80 23) (workarea 0 0 80 23)) where 'left' and 'top' values are zero. > IOW, in 10 years, would you be able to remember and explain why we use > zero instead of 'left' and 'top'? Adding a comment to the source code will help.