all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: 14765@debbugs.gnu.org
Subject: bug#14765: 24.3.50; desktop-restore-frames on NS does not work
Date: Tue, 2 Jul 2013 15:48:12 +0200	[thread overview]
Message-ID: <CAAeL0SR4Kd3eh1KAGjWJ4uY4nmMOmdFE2UKtmbstaQ7T1oTt2w@mail.gmail.com> (raw)
In-Reply-To: <3C13CE5D-BCB3-4272-84E0-783BB84F000C@swipnet.se>

On Tue, Jul 2, 2013 at 2:20 PM, Jan Djärv <jan.h.d@swipnet.se> wrote:

> Saving frames on NS (OSX or GnuStep) does not work.
> It only restores one frame, the last one created, no matter how many
> frames where saved (I tried, two, three and four).

> Error restoring frame: "Don't know how to interpret display \"\"zeplin.localdomain\"\"" [2 times]

With the current code, the first frame is not created, just reused.
For the others, desktop--restore-frames is calling
make-frame-on-display and passing it the expected display and the
saved frame info.

The expected display, assuming that you didn't set
`destop-restore-in-current-display', is the value of the saved frame's
display property (i.e., the result of (cdr (assq 'display config)). In
this case, "zeplin.localdomain".

So the question is, what happens if you do M-: (make-frame-on-display
"zeplin.localdomain") <RET>?

If that works, then it is possible that the make-frame-on-display is
failing because of other frame parameters; please try with just two
frames and show the contents of desktop--saved-states.





  parent reply	other threads:[~2013-07-02 13:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02 12:20 bug#14765: 24.3.50; desktop-restore-frames on NS does not work Jan Djärv
2013-07-02 13:11 ` martin rudalics
2013-07-02 13:48 ` Juanma Barranquero [this message]
2013-07-02 17:34   ` Jan Djärv
2013-07-02 17:38     ` Juanma Barranquero
2013-07-02 18:09       ` Jan Djärv
2013-07-02 18:16         ` Jan Djärv
2013-07-02 18:53         ` Juanma Barranquero
2013-07-02 18:59           ` Jan Djärv
2013-07-02 19:00             ` Juanma Barranquero

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAeL0SR4Kd3eh1KAGjWJ4uY4nmMOmdFE2UKtmbstaQ7T1oTt2w@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=14765@debbugs.gnu.org \
    --cc=jan.h.d@swipnet.se \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.