From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: GUI vs TTY when saving & restoring framesets
Date: Mon, 23 Jan 2017 11:16:42 -0500 [thread overview]
Message-ID: <jwv1svtpxn7.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: CAAeL0SQcAONrk4UZKtG2J0j2CGOAdRBfqOwNVYgO9TvjRuxCPg@mail.gmail.com
> 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
prev parent reply other threads:[~2017-01-23 16:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 4:21 GUI vs TTY when saving & restoring framesets Juanma Barranquero
2017-01-22 4:23 ` Juanma Barranquero
2017-01-22 13:27 ` Alan Mackenzie
2017-01-22 16:31 ` Eli Zaretskii
2017-01-22 18:00 ` Alan Mackenzie
2017-01-22 18:14 ` Eli Zaretskii
2017-01-22 18:55 ` Alan Mackenzie
2017-01-22 19:11 ` Eli Zaretskii
2017-01-22 19:38 ` Alan Mackenzie
2017-01-22 20:03 ` Eli Zaretskii
2017-01-22 20:44 ` Alan Mackenzie
2017-01-22 21:06 ` Juanma Barranquero
2017-01-23 17:39 ` Andreas Schwab
2017-01-23 18:02 ` martin rudalics
2017-01-22 16:23 ` Eli Zaretskii
2017-01-22 21:15 ` Juanma Barranquero
2017-01-23 3:36 ` Eli Zaretskii
2017-01-23 14:15 ` Juanma Barranquero
2017-01-23 15:49 ` Eli Zaretskii
2017-01-23 16:14 ` Juanma Barranquero
2017-01-23 16:16 ` Stefan Monnier [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=jwv1svtpxn7.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.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).