From: John Covici <covici@ccs.covici.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24298@debbugs.gnu.org
Subject: bug#24298: 25.1; problem with restoring desktop
Date: Thu, 25 Aug 2016 15:30:23 -0400 [thread overview]
Message-ID: <m3eg5csl2o.wl-covici@ccs.covici.com> (raw)
In-Reply-To: <831t1cejxb.fsf@gnu.org>
On Thu, 25 Aug 2016 15:18:56 -0400,
Eli Zaretskii wrote:
>
> > Date: Thu, 25 Aug 2016 15:04:11 -0400
> > From: John Covici <covici@ccs.covici.com>
> > Cc: rudalics@gmx.at, 24298@debbugs.gnu.org
> >
> > > Please look in the .emacs.desktop file itself. It's a text file, so
> > > is human-readable.
> >
> > And the order does correspond to what I see in the buffer list. Aside
> > from the damage of restoring the desktop in a version which broke the
> > restore, it looks like I had it before the problem started.
>
> Sorry, I'm confused: when you say "I had it", what do you mean by
> "it"?
I mean the order of the buffers before I used a version with the
problem.
>
> The desktop file records the buffer that was current in each frame, as
> part of the "frameset" at the beginning of the file, and then it
> records the list of buffers unrelated to frames. Does the frameset
> state the buffers correctly?
What is in the framset is correct, but when the bug is present another
buffer is made current.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
covici@ccs.covici.com
next prev parent reply other threads:[~2016-08-25 19:30 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 [this message]
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
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=m3eg5csl2o.wl-covici@ccs.covici.com \
--to=covici@ccs.covici.com \
--cc=24298@debbugs.gnu.org \
--cc=eliz@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).