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 20:14:03 +0200 [thread overview]
Message-ID: <83o9yz3qtw.fsf@gnu.org> (raw)
In-Reply-To: <20170122180010.GB12823@acm> (message from Alan Mackenzie on Sun, 22 Jan 2017 18:00:10 +0000)
> Date: Sun, 22 Jan 2017 18:00:10 +0000
> Cc: lekktu@gmail.com, emacs-devel@gnu.org
> From: Alan Mackenzie <acm@muc.de>
>
> #23630 is not fixed. I've just tried it.....
>
> > FWIW, when I finished working on bug#24298, I no longer saw incorrect
> > order of buffers after restoring the desktop: their order was always
> > the same, as long as I restored from the same desktop file. Maybe you
> > just don't like the order in which desktop.el puts them in the desktop
> > file?
>
> ... on master. I had four frames open, cycled through them, then did
> C-x C-c, creating the desktop file and exiting.
>
> I restarted Emacs, which created the four frames, and then did C-x C-b.
> The second entry there was *scratch*. This was not any of the four
> buffers which were in the frames' windows when I previously shut down.
??? The *scratch* buffer is created in any Emacs session regardless of
the saved desktop. So why isn't the above TRT? When did Emacs and
desktop.el behave differently?
> Other than that, the order of the buffers in C-x C-b is the reverse of
> the order in my desktop file.
Why is that a problem? The order of buffers in the desktop file is
not something a user is supposed to look at, or care about.
next prev parent reply other threads:[~2017-01-22 18:14 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 [this message]
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
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=83o9yz3qtw.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).