From: Juanma Barranquero <lekktu@gmail.com>
To: Alan Mackenzie <acm@muc.de>
Cc: Eli Zaretskii <eliz@gnu.org>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: GUI vs TTY when saving & restoring framesets
Date: Sun, 22 Jan 2017 22:06:42 +0100 [thread overview]
Message-ID: <CAAeL0SQ_zmv=qTHgoS7V+ZV3FE8i2t4pLx-VOECE+V+1Hjx5aA@mail.gmail.com> (raw)
In-Reply-To: <20170122193841.GD12823@acm>
[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]
On Sun, Jan 22, 2017 at 8:38 PM, Alan Mackenzie <acm@muc.de> wrote:
> 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. Anyhow, I've had this use of <fn> for 15
> years now, and 15 years ago there was nothing like frames in the desktop
> file.
Well, frameset restoration is a new feature, which does not interfere with
what you did before. It just does not do what you want in a new situation
(you could always set desktop-restore-frames to nil and not lose any old
functionality). I don't mean that your use case is not valid or relevant,
only that it is hardly surprising that it doesn't work out of the box ;-)
> I
> think it more likely that Juanma didn't see any need to preserve the
> association of particular frames with particular buffers when extending
> desktop to handle frames.
I tried to preserve anything that I could imagine being even remotely
useful, or being told so. Obviously, there's room for improvement.
> But it would
> be nice if desktop could preserve the ordering of the frames and buffers,
> too.
I'll look into it.
[-- Attachment #2: Type: text/html, Size: 1571 bytes --]
next prev parent reply other threads:[~2017-01-22 21:06 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 [this message]
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='CAAeL0SQ_zmv=qTHgoS7V+ZV3FE8i2t4pLx-VOECE+V+1Hjx5aA@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=acm@muc.de \
--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 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).