From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: GUI vs TTY when saving & restoring framesets
Date: Sun, 22 Jan 2017 22:15:14 +0100 [thread overview]
Message-ID: <CAAeL0STnZNeyCQXhbqym+vkyYhAL8+4=Z70oqE7qqKWrP+jzJg@mail.gmail.com> (raw)
In-Reply-To: <834m0r5aiu.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]
On Sun, Jan 22, 2017 at 5:23 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> If you can find a way of fixing 17693 without disabling frameset
> restoration, feel free to do that on master.
I'm going to take a hard look at this and every frameset bug I can find.
I'll revert the frameset.el and desktop.el code (locally, not on the
repository) to its previous state and will try to understand the issues and
the possible fixes. (I'm not implying the current fixes aren't good, only
that I still don't understand their implications).
> 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).
> As for the trips in frameset.el, I don't think they are entirely
> redundant, because I'd expect the following sequence of Emacs
> invocations to re-create the original GUI frames from the 1st
> invocation:
>
> . emacs
> . emacs -nw
> . emacs
That is exactly what worked before (or, at least, it worked in all my
tests) and it's broken now.
[-- Attachment #2: Type: text/html, Size: 1887 bytes --]
next prev parent reply other threads:[~2017-01-22 21:15 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAeL0STnZNeyCQXhbqym+vkyYhAL8+4=Z70oqE7qqKWrP+jzJg@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=eliz@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.