From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: GUI vs TTY when saving & restoring framesets
Date: Mon, 23 Jan 2017 05:36:37 +0200 [thread overview]
Message-ID: <83d1fe4fcq.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0STnZNeyCQXhbqym+vkyYhAL8+4=Z70oqE7qqKWrP+jzJg@mail.gmail.com> (message from Juanma Barranquero on Sun, 22 Jan 2017 22:15:14 +0100)
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Sun, 22 Jan 2017 22:15:14 +0100
> Cc: Emacs developers <emacs-devel@gnu.org>
>
> > Given user feedback we
> > have, I think we should not create GUI frames when Emacs is invoked
> > with -nw, though, at least by default.
>
> I don't understand this. Creating GUI frames in a -nw session shouldn't happen. "Mimicking" the GUI frames in
> the -nw session is what the code intended to do, so if you have three frames of whatever size and other
> parameters, the TTY session would start with three tty frames (F1 to F3). Then going back to GUI mode would
> restore the original GUI frames (not the tty ones).
That's fine with me, but if you read bug#17693, you will see that the
original report there explicitly describes a situation where GUI
frames were created by restoring desktop in a -nw session. I thought
this was a feature, but if you say it's a bug, fixing it will fulfill
user expectations.
> > . emacs
> > . emacs -nw
> > . emacs
>
> That is exactly what worked before (or, at least, it worked in all my tests) and it's broken now.
Because the original code had worse problems, and we didn't know how
to fix it better than that.
next prev parent reply other threads:[~2017-01-23 3:36 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 [this message]
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
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=83d1fe4fcq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
/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).