From: Eli Zaretskii <eliz@gnu.org>
To: Mark Jamsek <mark@bsdbox.org>
Cc: larsi@gnus.org, 54140@debbugs.gnu.org
Subject: bug#54140: 27.2; desktop-save-mode fails to restore frame and window config
Date: Fri, 25 Feb 2022 14:02:33 +0200 [thread overview]
Message-ID: <83lexzqhly.fsf@gnu.org> (raw)
In-Reply-To: <9D4B6AB3-A358-4B36-85DB-8F0AA5131CD1@bsdbox.org> (message from Mark Jamsek on Fri, 25 Feb 2022 20:39:21 +1100)
> From: Mark Jamsek <mark@bsdbox.org>
> Date: Fri, 25 Feb 2022 20:39:21 +1100
> Cc: larsi@gnus.org, 54140@debbugs.gnu.org
>
> There's no need to debug this: this is the expected behavior on TTY
> frames
>
> Is this documented; if not, would a patch to this effect be accepted?
It depends on what the patch will do. Unconditionally letting desktop
restore the frameset on TTY displays is out of the question, as it
will bring back the problems we solved when we prevented that.
> see desktop-restoring-frameset-p. We deliberately don't
> restore the frameset on text-mode displays. For the reasons, see
> bug#17693.
>
> I had a cursory look but don’t quite understand why that precludes desktop-save-mode from working with
> Emacs in the terminal. If you save an -nw session, you’d have no graphical frames to restore when starting
> an -nw session.
How do we know that the desktop was saved from a -nw session?
> I’ll read the thread in its entirety when back in front of the kb.
Thanks. A related issue is bug#24298.
prev parent reply other threads:[~2022-02-25 12:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 10:04 bug#54140: 27.2; desktop-save-mode fails to restore frame and window config Mark Jamsek
2022-02-24 14:30 ` Lars Ingebrigtsen
[not found] ` <14B9A1B4-2208-4C05-8167-DAF3DC49C3D6@bsdbox.org>
2022-02-25 2:38 ` Lars Ingebrigtsen
2022-02-25 2:58 ` Mark Jamsek
2022-02-25 8:02 ` Eli Zaretskii
2022-02-25 9:39 ` Mark Jamsek
2022-02-25 12:02 ` Eli Zaretskii [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83lexzqhly.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54140@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mark@bsdbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).