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: Mon, 30 Sep 2019 10:10:30 +0200	[thread overview]
Message-ID: <CAAeL0SSBy-ycLnrszGJSKCvp7_Em-NPRWoDcZzBOL2xZDYYSvw@mail.gmail.com> (raw)
In-Reply-To: <87pnji8ki4.fsf@gnus.org>

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

On Mon, Sep 30, 2019 at 6:40 AM Lars Ingebrigtsen <larsi@gnus.org> wrote:

> It sounds like we should perhaps refer users to the C-x r f a command
> instead...

Currently, the function assigned to the C-x r map to save a frameset saves
all the frames, so in some uses, saving and restoring the window
configuration (which affects just one frame) is faster and cleaner. Also,
restoring a frameset not only restores the window configuration, but also
position on the screen.

Of course, it would be possible to add another command, or a prefix
parameter, to frameset-to-register, to save just the selected frame, and to
restore the frameset without moving the frame.

> But in any case, desktop.el probably shouldn't be saving
> these useless window configuration registers.

Definitely. It's wasted space and time, and does not serve any useful
purpose.

FWIW, I agree. Documenting the issue and filtering out the
window-configurations on desktop save seems like the easier answer right
now. Don't think it's really a very urgent or frequent issue.

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

  reply	other threads:[~2019-09-30  8:10 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
2019-09-30  8:10         ` Juanma Barranquero [this message]
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=CAAeL0SSBy-ycLnrszGJSKCvp7_Em-NPRWoDcZzBOL2xZDYYSvw@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).