unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: covici@ccs.covici.com
Cc: 24298@debbugs.gnu.org
Subject: bug#24298: Acknowledgement (25.1; problem with restoring desktop)
Date: Sat, 10 Dec 2016 17:50:05 +0200	[thread overview]
Message-ID: <83mvg3g4wi.fsf@gnu.org> (raw)
In-Reply-To: <m3inqr96a4.wl-covici@ccs.covici.com> (message from John Covici on Sat, 10 Dec 2016 10:02:11 -0500)

> Date: Sat, 10 Dec 2016 10:02:11 -0500
> From: John Covici <covici@ccs.covici.com>
> Cc: 24298@debbugs.gnu.org
> 
> I can reproduce this with a  desktop with just two buffers, what
> happens is when the commit is there, the wrong buffer is the current
> one and  if I do c-x-b it has the scratch buffer as the next one
> rather than the previous buffer.  For instance in the desktop I will
> send you, the current buffer is the Makefile, but when I restore the
> desktop, default.xml is made the current buffer instead and the
> scratch buffer is the default for c-x-b.

The desktop file you sent doesn't have Makefile, it has default.xml
and brltty-9999.ebuild.  The buffer that's expected to be the current
one after restoring is the first one in the list, and in your case
it's default.xml.  So if that buffer becomes the current after
restoring desktop, I don't see a problem in the restore stage, and
don't understand how that commit could have changed this.

What do you see in the list returned by buffer-list, before you end a
session?  The buffers are recorded in the desktop file in the order
they appear in that list, and in my case, this is the current buffer
when I invoke desktop-save.





  reply	other threads:[~2016-12-10 15:50 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24 11:31 bug#24298: 25.1; problem with restoring desktop John Covici
2016-08-24 14:23 ` Eli Zaretskii
2016-08-24 14:53   ` John Covici
2016-08-24 15:11     ` Eli Zaretskii
2016-08-25  1:32       ` John Covici
2016-08-24 15:46 ` martin rudalics
2016-08-24 16:02   ` Eli Zaretskii
2016-08-24 20:57     ` N. Jackson
2016-08-25  9:16       ` martin rudalics
2016-08-25 13:09         ` N. Jackson
2016-08-25 14:52           ` Eli Zaretskii
2016-08-25  9:16     ` martin rudalics
2016-08-25 14:48       ` Eli Zaretskii
2016-08-25 15:31         ` John Covici
2016-08-25 16:22           ` Eli Zaretskii
2016-08-25 18:22             ` John Covici
2016-08-25 18:30               ` Eli Zaretskii
2016-08-25 19:04                 ` John Covici
2016-08-25 19:18                   ` Eli Zaretskii
2016-08-25 19:30                     ` John Covici
2016-08-25  1:33   ` John Covici
2016-08-25  9:17     ` martin rudalics
2016-08-25 10:56       ` John Covici
2016-08-25 12:27         ` martin rudalics
2016-08-25 14:50           ` Eli Zaretskii
     [not found] ` <handler.24298.B.14720383029936.ack@debbugs.gnu.org>
2016-12-04  1:51   ` bug#24298: Acknowledgement (25.1; problem with restoring desktop) John Covici
2016-12-04 15:28     ` Eli Zaretskii
2016-12-04 15:34       ` John Covici
2016-12-10 14:19         ` Eli Zaretskii
2016-12-10 15:02           ` John Covici
2016-12-10 15:50             ` Eli Zaretskii [this message]
2016-12-10 16:02               ` John Covici
2016-12-10 17:47                 ` Eli Zaretskii
2016-12-10 18:46                   ` John Covici
2016-12-17 13:11                     ` Eli Zaretskii
2016-12-17 14:05                       ` John Covici
2016-12-17 14:46                         ` Eli Zaretskii
2016-12-17 16:41                           ` John Covici
2016-12-17 17:07                             ` Eli Zaretskii

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=83mvg3g4wi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24298@debbugs.gnu.org \
    --cc=covici@ccs.covici.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).