unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 17090@debbugs.gnu.org
Subject: bug#17090: desktop.el saves unusable register data in register-alist
Date: Sun, 29 Sep 2019 18:17:24 +0200	[thread overview]
Message-ID: <CAAeL0SSGS9dtSAfo2i1yKOVQr4T3VmW7TxMbKdTXmtPB09Dx6g@mail.gmail.com> (raw)
In-Reply-To: <87a7angnbk.fsf@gnus.org>

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

Curious that my original recipe (fixing the C-x C-x to C-x C-c, as I
suppose I intended) doesn't work now because

  emacs -Q -f desktop-read

does not read the desktop file from the current directory ('.' is no longer
in desktop-path).

But anyway, back to the issue:

> Hm, I think I was wrong here -- I'm not getting exactly the same errors
> as in earlier versions of Emacs, but the data that's saved still isn't
> usable.

Correct.

But, I suppose it is perhaps not worth fixing now, because after that we
implemented framesets, and you can do

C-x r f a

and the frameset in register a is saved and correctly reloaded afterwards.
It's a bit of an overkill, of course.

If we want to fix it, perhaps we could trick our way, by using framesets to
save a one-frame frameset with some special info to mark that it is really
intended to be just a window-configuration, and then, when reloading the
desktop, restoring somehow the window configuration into the register, from
the frameset data. No idea if it is worth the effort, but I think it would
be doable.

[-- Attachment #2: Type: text/html, Size: 1319 bytes --]

  reply	other threads:[~2019-09-29 16:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24 20:31 bug#17090: desktop.el saves unusable register data in register-alist Juanma Barranquero
2019-09-29 14:42 ` Lars Ingebrigtsen
2019-09-29 14:59   ` Lars Ingebrigtsen
2019-09-29 16:17     ` Juanma Barranquero [this message]
2019-09-30  4:40       ` Lars Ingebrigtsen
2019-09-30  8:10         ` Juanma Barranquero
2019-10-07 18:28       ` Juri Linkov

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=CAAeL0SSGS9dtSAfo2i1yKOVQr4T3VmW7TxMbKdTXmtPB09Dx6g@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=17090@debbugs.gnu.org \
    --cc=larsi@gnus.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).