From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: GUI vs TTY when saving & restoring framesets
Date: Sun, 22 Jan 2017 22:03:57 +0200 [thread overview]
Message-ID: <83inp650b6.fsf@gnu.org> (raw)
In-Reply-To: <20170122193841.GD12823@acm> (message from Alan Mackenzie on Sun, 22 Jan 2017 19:38:41 +0000)
> Date: Sun, 22 Jan 2017 19:38:41 +0000
> Cc: lekktu@gmail.com, emacs-devel@gnu.org
> From: Alan Mackenzie <acm@muc.de>
>
> > I always have several frames in my sessions, each one with its buffer,
> > and when I restore the sessions, each frame comes up with the same
> > buffer it had when I shut down Emacs, no complicated frame-walking
> > dance necessary, neither before shutting down Emacs nor after
> > restarting it.
>
> Something similar happens when I use the defaults. But the buffers come
> up in the "wrong" frames (i.e. associated with a different <fn> key),
> making it not useful for me.
Then perhaps the problem is that the frame names are jumbled after
restoring them, something that "normal" usage will never reveal, as
most people don't care about the internal numbering of frames, and I
don't think there was a requirement to keep them when restoring.
next prev parent reply other threads:[~2017-01-22 20:03 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 [this message]
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
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=83inp650b6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--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).