From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 17090@debbugs.gnu.org
Subject: bug#17090: desktop.el saves unusable register data in register-alist
Date: Mon, 30 Sep 2019 06:40:19 +0200 [thread overview]
Message-ID: <87pnji8ki4.fsf@gnus.org> (raw)
In-Reply-To: <CAAeL0SSGS9dtSAfo2i1yKOVQr4T3VmW7TxMbKdTXmtPB09Dx6g@mail.gmail.com> (Juanma Barranquero's message of "Sun, 29 Sep 2019 18:17:24 +0200")
Juanma Barranquero <lekktu@gmail.com> writes:
> 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.
It sounds like we should perhaps refer users to the C-x r f a command
instead... But in any case, desktop.el probably shouldn't be saving
these useless window configuration registers.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-09-30 4:40 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
2019-09-30 4:40 ` Lars Ingebrigtsen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnji8ki4.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=17090@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.