From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 15071-done@debbugs.gnu.org
Subject: bug#15071: 24.3.50; desktop-read: frameset-states accessing a non-frameset
Date: Sun, 11 Aug 2013 19:00:36 +0200 [thread overview]
Message-ID: <DD12C8B7-4381-4844-ACEE-04CBC9B5FED9@swipnet.se> (raw)
In-Reply-To: <18A3846B-FFAC-4A35-8CE3-4144951543CE@swipnet.se>
Hello.
Turns out a make bootsrap was needed. I should have figured that out, nowdays bootstrap is required for almost everytime a bzr up is done. Sorry for the noice.
Closing.
Jan D.
11 aug 2013 kl. 18:42 skrev Jan Djärv <jan.h.d@swipnet.se>:
> Hello.
>
> 11 aug 2013 kl. 18:21 skrev Juanma Barranquero <lekktu@gmail.com>:
>
>>> desktop-read: frameset-states accessing a non-frameset
>>
>> I cannot directly load you desktop because of a couple of invalid
>> values (font and border-width), but once I set them to reasonable
>> values for my system, and leaving everything else as is, it loads just
>> fine.
>>
>> Please, try to reproduce the problem starting from emacs -Q, without
>> customizations or anything else.
>>
>
> Ok,
> emacs -Q
> M-x desktop-save (in ~).
> C-x C-c
> emacs -Q
> M-x desktop-read
>
> Same message.
>
> Attaching that .emacs.desktop.
>
> What is an "invalid value"? Something not supported by your system? I would not call that invalid, it is perfectly valid, you just can't use it. Or if it indeed is invalid, that is a bug in desktop, it is saved by desktop.
>
> Jan D.
>
> <emacs.desktop>
next prev parent reply other threads:[~2013-08-11 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 15:50 bug#15071: 24.3.50; desktop-read: frameset-states accessing a non-frameset Jan Djärv
2013-08-11 16:21 ` Juanma Barranquero
2013-08-11 16:42 ` Jan Djärv
2013-08-11 17:00 ` Jan Djärv [this message]
2013-08-11 17:03 ` 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=DD12C8B7-4381-4844-ACEE-04CBC9B5FED9@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=15071-done@debbugs.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 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.