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 16:19:07 +0200 [thread overview]
Message-ID: <83pokzg944.fsf@gnu.org> (raw)
In-Reply-To: <m3twajaesy.wl-covici@ccs.covici.com> (message from John Covici on Sun, 04 Dec 2016 10:34:37 -0500)
> Date: Sun, 04 Dec 2016 10:34:37 -0500
> From: John Covici <covici@ccs.covici.com>
> Cc: 24298@debbugs.gnu.org
>
> On Sun, 04 Dec 2016 10:28:23 -0500,
> Eli Zaretskii wrote:
> >
> > > Date: Sat, 03 Dec 2016 20:51:48 -0500
> > > From: John Covici <covici@ccs.covici.com>
> > >
> > > OK, doing a git bisect, I found the commit which breaks my desktop
> > > restore -- I am using a text console here.
> > >
> > > [c9f7ec736b78bef5359b6da03296277c535e8e89] * lisp/desktop.el: Disable
> > > restore frameset if in non-graphic display.
> >
> > Does this mean you have more than one frame in your text-terminal
> > sessions, after restoring the desktop? What effect does the following
> > command produce after you restore the session?
> >
> > C-x 5 o
> >
> > If you have more than one frame, you should now see "Fn" at the left
> > edge of the mode line, where n is a small integer, which is different
> > from the one you saw there before the above command.
>
> Nope, this is a text console, the command does nothing.
Then I'm afraid I cannot reproduce this. I tried restoring my desktop
in "emacs -nw" several times, and each time I end up looking at the
same 2 buffers displayed in 2 windows one below the other.
Could you perhaps create the smallest desktop file that reproduces
this problem for you, and post it? I'd like to experiment with it.
Thanks.
next prev parent reply other threads:[~2016-12-10 14:19 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 [this message]
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=83pokzg944.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).