unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: GUI vs TTY when saving & restoring framesets
Date: Sun, 22 Jan 2017 18:00:10 +0000	[thread overview]
Message-ID: <20170122180010.GB12823@acm> (raw)
In-Reply-To: <831svv5a4l.fsf@gnu.org>

Hello, Eli.

On Sun, Jan 22, 2017 at 18:31:54 +0200, Eli Zaretskii wrote:
> > Date: Sun, 22 Jan 2017 13:27:27 +0000
> > From: Alan Mackenzie <acm@muc.de>
> > Cc: Emacs developers <emacs-devel@gnu.org>

> > To those bugs I would add:
> > #23630: Emacs 25.0.94.1: desktop-read loads buffers in the wrong order.
> > #19706: Emacs 25.0.50; (+ nil nil -1) in desktop-restore-frameset

> When were those last tried?  Is it possible that they are fixed on the
> release branch?

#19706 had a workaround applied to it, I think.  (I think I did this
myself)
#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.

Other than that, the order of the buffers in C-x C-b is the reverse of
the order in my desktop file.

This was in GNU, X-Windows, with desktop-restore-frames set to t, using
version 208 (i.e. Emacs >= 25) of the desktop file format.

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2017-01-22 18:00 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 [this message]
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
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=20170122180010.GB12823@acm \
    --to=acm@muc.de \
    --cc=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).